From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/13640 Path: news.gmane.org!.POSTED.ciao.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Possibly spurious EAGAIN seen in pthread_key_create on x86 Date: Tue, 22 Jan 2019 19:57:01 -0500 Message-ID: <20190123005701.GU23599@brightrain.aerifal.cx> References: <7ccdc4b9-c06e-5c76-6783-38f9cf297a14@adelielinux.org> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: ciao.gmane.org; posting-host="ciao.gmane.org:195.159.176.228"; logging-data="188958"; mail-complaints-to="usenet@ciao.gmane.org" User-Agent: Mutt/1.5.21 (2010-09-15) To: musl@lists.openwall.com Original-X-From: musl-return-13656-gllmg-musl=m.gmane.org@lists.openwall.com Wed Jan 23 01:57:22 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by ciao.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1gm6qy-000n03-Lw for gllmg-musl@m.gmane.org; Wed, 23 Jan 2019 01:57:16 +0100 Original-Received: (qmail 1784 invoked by uid 550); 23 Jan 2019 00:57:14 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 1763 invoked from network); 23 Jan 2019 00:57:13 -0000 Content-Disposition: inline In-Reply-To: <7ccdc4b9-c06e-5c76-6783-38f9cf297a14@adelielinux.org> Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:13640 Archived-At: On Tue, Jan 22, 2019 at 03:15:35PM -0600, A. Wilcox wrote: > Hello there muslers, > > While running the test suite for GLib++ (the C++ wrapper for GLib) on > our 32-bit x86 builder (i686), after upgrading to 1.1.21, it logged: > > > FAIL: glibmm_mainloop/test > ========================== > GLib (gthread-posix.c): Unexpected error from C library during > 'pthread_key_create': Resource temporarily unavailable. Aborting. > > > Running the test suite an additional 160 (one hundred and sixty) times > could not repeat the result. Still, I wanted to report it on the > off-chance there is some significance to this single result. > > Importantly, I haven't noticed this failure on any of the other > architectures we've built GLib++ on (ppc32, ppc64, aarch64). Can you figure out what this test is doing, or point to source so others can? My best guess is that it's creating and destroying keys very many times, and something happened that caused the dirty-slot reclaiming __synccall to fail (maybe EMFILE or ENFILE?). Rich