From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24915 invoked by alias); 26 Aug 2014 18:11:20 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Received: (qmail 24864 invoked by uid 48); 26 Aug 2014 18:11:15 -0000 From: "sstewartgallus00 at mylangara dot bc.ca" To: glibc-bugs@sourceware.org Subject: [Bug nptl/17214] Expose a function to reset the PID cache Date: Tue, 26 Aug 2014 18:11:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: nptl X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sstewartgallus00 at mylangara dot bc.ca X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-08/txt/msg00108.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=17214 --- Comment #7 from Steven Stewart-Gallus --- Strange, Rich. The source in pthread_join says: /* Wait for the child. */ lll_wait_tid (pd->tid); However, I'm sure I wasn't mistaken when my code was randomly failing at unshare(CLONE_NEWPID). The idea that the pthread_join completed before the kernel recognized the thread as dead seemed very logical to me but I may be wrong. Alternatively, there could a tiny bug in the kernel or in GLibc as this logic is probably infreguently tested. I'll try to create a reduced test for the problem. In any case, unshare(CLONE_NEWPID); then fork is kind of fragile and weird (for one, the spawned process after fork doesn't get immunity to signals like an init should). -- You are receiving this mail because: You are on the CC list for the bug.