Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #16772

Re: Is this a bug?

Path csiph.com!goblin2!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From George R Goffe <grgoffe@yahoo.com>
Newsgroups gnu.bash.bug
Subject Re: Is this a bug?
Date Tue, 18 Aug 2020 21:14:38 +0000 (UTC)
Lines 82
Approved bug-bash@gnu.org
Message-ID <mailman.280.1597785290.2469.bug-bash@gnu.org> (permalink)
References <1361377909.989786.1596736417780.ref@mail.yahoo.com> <1361377909.989786.1596736417780@mail.yahoo.com> <0d88a4ca-9eca-62b4-91bd-d2e4083190f3@case.edu> <1312274972.4025864.1597785278610@mail.yahoo.com>
Reply-To George R Goffe <grgoffe@yahoo.com>
NNTP-Posting-Host lists.gnu.org
Mime-Version 1.0
Content-Type text/plain; charset=UTF-8
Content-Transfer-Encoding quoted-printable
X-Trace usenet.stanford.edu 1597785290 30021 209.51.188.17 (18 Aug 2020 21:14:50 GMT)
X-Complaints-To action@cs.stanford.edu
To "bug-bash@gnu.org" <bug-bash@gnu.org>, Chet Ramey <chet.ramey@case.edu>
Envelope-to bug-bash@gnu.org
DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1597785283; bh=UsAn8oSMXt0Lv/0LfmLfCgqbe4YEUscUX7XhvqFR5vg=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=jSObPExbUMoL108hzYVVBqWNmq/s0XCTQl9fzVrhz3SXBas/eM5HoRoWq0KWcYAds/au4JZvfDQtER3Le4x9ExvmQXiFbSlYNjhT5qrPMZ3VOIq8DHZYdK2ebnNvv3PmkaiJI8PKKBJuJRi+Qsz5y+rmXvPKuSt8P1S2fOrK2rdUnYK03WKcoBOc8zVwOLl2WGstyJ2M+KmMnNgAOXqvvY2MRB8GX0f24N/yJqER4jF6090GsS7jZwdLfgCbRyE0Ie2cxevSLu3fcy5sDF/TcUVhvr38QzN4OKV/Hb2ZbQHq5xXRuJpCh/H8L/382P5kZUlv7QumLp75tiuwJ8Gd/w==
X-YMail-OSG ozLtknIVM1nfJWPvQ6aHOaOIC19HRR87LOSpVcXCTOkIEK9mRiY3p2NP9b9e2fX 8ze8cAx.iV_OsrDyGyLtZcoXbpWjtRcx1fZU4WzGA29K1Kz6BQKxanhg_iSrzWezTzM4v1WnQLm5 5vXOMpTYfI2IiEg4HVdrGINr7udBm5bqmbtAR2FgmLXUfTac7bdmaydrKZUl34hqrCnqMUh22bN3 mr5JMqgsqBDDCfQUG9jVxfO3.56bfsnGDByjQ9tAeHNjLQm7BCyERUZ7DZHMC6HAKO3UgJAnHjNe WvotRm65YOeyDkiKQkprCjI5DbHbFuvD99I.fETZjEI4aXzfoCJ0Iz4lNgs_WZ2ivE85UIDih53D vKXO68vsI2ySUDKVv0O_Mp3dkDI7WUUduMO6w.6l3rk7gHffH51ez2jp1Kx2uUP4GoLyHw1l.Mk4 WYePeQ7PYIYn2LsOwoVJLiJ2wH9Z1iuEc71c8NtzKMQqd5XDy1UqS6h3dfb9Ah3bAQP7lsSIlwtg qc7Fg1GG4IE5ejZPqigKAQVWNgRLTprbJocJp.a0cKAsjH78TP6yHnm0N1USu3GyL.sxOauoHJqi iyAoq9JjYGS2oewuWBKC84kxckQjuz0A7HWlxxDOgvb4YB6IlN.CD20rlneVTp9ABlRN.lIevC_7 8izbr2kRMNYG3u9cjkfpAx0F7MN3KknCppU90_AHeYdBp0x6ds_Sct.K5OJuqnKi7xOkcwy.2LRw JR6ADMoyNuOZiTFhohooi03GfwPIzez7MqQHCDws.PfYtlD5w2n2rzRFrwFYmMsqIfsNAqBABp_I iHfpsTY7vEpb9QiSGBu9jCZSUXo9Iqmx2uYWI.gCCxTj6T2MDTIPlhIFCRrZPFA_PGScYmDC4nTT Ubqikg7K7WBXJ8BqfV7baMr_O4.GO06vtKdAR7ONk64AkTQjahw9dG15hAAG84utPHDyZ4DhxZoZ V9at3dAdvZaXNGewYPtN7ptZzchoDN9Qe9lUOFBnOO04hpn.NSjwuf8hXg5ng_YSrOutoh_oh.h3 CcSmu_0CS8.K5EwGjq7fDSkpPr.7b8f1uK0Jv8DKPJj8oxln0t.01kXTL6bls0XzG6neCISW29WL _HwR2gwHiR4e36zz059ttHCVOc0kBsVgBze83v2Nmx2Lr9xqTBrerEVnvMhoWB0prjC1wJeTdGEu YU_t2DN7KPIVpjMl9LG0ANJ0kTCQt1MMZ1rc7JYQ83lwquWJYhsjykrGzBedTbsekT801W8syMNV DMZJFFAi55bQ5gv2BXJrK1mHqeDJ5APKk3rjMFlbXoYQpasZAjGj0K6GcxCLJSj2Pq_u61dXif8Y ah_Jpcgur6u3D4Ca424Ij.veL82x3hTTVvcWw.u8b56949lCXk7m9ZwZPAquawH1Iq2wqUGYcquB g9HBH
In-Reply-To <0d88a4ca-9eca-62b4-91bd-d2e4083190f3@case.edu>
X-Mailer WebService/1.1.16455 YMailNorrin Mozilla/5.0 (X11; Linux x86_64; rv:81.0) Gecko/20100101 Firefox/81.0
Content-Length 2522
Received-SPF pass client-ip=66.163.189.84; envelope-from=grgoffe@yahoo.com; helo=sonic306-22.consmr.mail.ne1.yahoo.com
X-detected-operating-system by eggs.gnu.org: First seen = 2020/08/18 17:14:43
X-ACL-Warn Detected OS = Linux 3.11 and newer [fuzzy]
X-Spam_score_int -30
X-Spam_score -3.1
X-Spam_bar ---
X-Spam_report (-3.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=ham autolearn_force=no
X-Spam_action no action
X-BeenThere bug-bash@gnu.org
X-Mailman-Version 2.1.23
Precedence list
List-Id Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive <https://lists.gnu.org/archive/html/bug-bash>
List-Post <mailto:bug-bash@gnu.org>
List-Help <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID <1312274972.4025864.1597785278610@mail.yahoo.com>
X-Mailman-Original-References <1361377909.989786.1596736417780.ref@mail.yahoo.com> <1361377909.989786.1596736417780@mail.yahoo.com> <0d88a4ca-9eca-62b4-91bd-d2e4083190f3@case.edu>
Xref csiph.com gnu.bash.bug:16772

Show key headers only | View raw


Chet,


Please accept my apology for not responding to your email sooner.

I have the bash source from the(?) repository. I followed Dimitris suggestion and found bash hung in a system call named "pselect". I did a grep on the source and found the only two ".c" files using "pselect":

Does this help?

Best regards and thanks for your patience.

George...


lib/readline/input.c:#if defined (HAVE_PSELECT)
lib/readline/input.c:#if defined (HAVE_PSELECT)
lib/readline/input.c:#if defined (HAVE_PSELECT)
lib/readline/input.c:      result = pselect (fileno (stream) + 1, &readfds, NULL, NULL, NULL, &_rl_orig_sigset);
lib/readline/input.c:      result = pselect (fileno (stream) + 1, &readfds, NULL, NULL, NULL, &empty_set);
lib/sh/ufuncs.c:#if defined (HAVE_TIMEVAL) && (defined (HAVE_SELECT) || defined (HAVE_PSELECT))
lib/sh/ufuncs.c:#if defined (HAVE_PSELECT)
lib/sh/ufuncs.c:#if defined (HAVE_PSELECT)
lib/sh/ufuncs.c:#endif /* !HAVE_PSELECT */
lib/sh/ufuncs.c:#if defined (HAVE_PSELECT)
lib/sh/ufuncs.c:      r = pselect(0, (fd_set *)0, (fd_set *)0, (fd_set *)0, &ts, &blocked_sigs);Chet,








On Thursday, August 6, 2020, 1:10:42 PM PDT, Chet Ramey <chet.ramey@case.edu> wrote: 





On 8/6/20 1:53 PM, George R Goffe wrote:
> Hi,
> 
> I apologize for bothering you with this question.
> 
> I have several directories on a system with > 300k files. When I use filename completion bash freezes for over a minute depending on the number of files. I'm pretty sure that bash has to read the directory to do the completion but the read appears to be uninterruptible. Is this a bug?

Can you tell what system call bash is executing? Some file systems make
the system call underlying readdir() uninterruptible.

In general, the readline filename completion function that calls readdir
only reads a single directory entry at a time, and returns it to a caller.
If the SIGINT causes readdir to return NULL, the function returns normally.
If readdir returns a valid entry, the caller (e.g., rl_completion_matches)
checks for receipt of a signal. That should be enough to terminate the
directory read.


> Again, I apologize for bothering you with this.


No bother.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
        ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

Back to gnu.bash.bug | Previous | Next | Find similar


Thread

Re: Is this a bug? George R Goffe <grgoffe@yahoo.com> - 2020-08-18 21:14 +0000

csiph-web