From: Roland McGrath <roland@redhat.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Ingo Molnar <mingo@elte.hu>, Petr Vandrovec <vandrove@vc.cvut.cz>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@zip.com.au>
Subject: Re: [patch] Re: Problem with exiting threads under NPTL
Date: Mon, 15 Dec 2003 15:06:53 -0800 [thread overview]
Message-ID: <200312152306.hBFN6riq024958@magilla.sf.frob.com> (raw)
In-Reply-To: Linus Torvalds's message of Sunday, 14 December 2003 12:38:15 -0800 <Pine.LNX.4.58.0312141228170.1478@home.osdl.org>
> Or is that case impossible to trigger? Looks a bit like that. But if it
> _is_ impossible to trigger (ie exit_signal cannot be -1 for a thread
> leader), then why does the current code test for "&& leader->exit_signal
> != -1)" at all?
I think that most of the logic testing exit_signal was written when
CLONE_DETACHED could be used independent of CLONE_THREAD. We concluded
that was unworkable due to some related races and changed clone so that the
situation of a (live) thread group leader with exit_signal == -1 is now
impossible.
prev parent reply other threads:[~2003-12-15 23:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-14 5:25 Petr Vandrovec
2003-12-14 15:02 ` Martin Schlemmer
2003-12-14 19:38 ` [patch] " Ingo Molnar
2003-12-14 20:38 ` Linus Torvalds
2003-12-14 20:45 ` Linus Torvalds
2003-12-14 21:02 ` Ingo Molnar
2003-12-15 15:04 ` Jörn Engel
2003-12-14 21:06 ` Ingo Molnar
2003-12-14 22:10 ` Linus Torvalds
2003-12-14 22:17 ` Ingo Molnar
2003-12-14 22:32 ` Linus Torvalds
2003-12-15 23:04 ` Roland McGrath
2003-12-14 22:28 ` Ingo Molnar
2003-12-14 22:45 ` Linus Torvalds
2003-12-14 23:08 ` Ingo Molnar
2003-12-15 6:31 ` dan carpenter
2003-12-15 11:43 ` Ingo Molnar
2003-12-15 13:07 ` dan carpenter
2003-12-15 15:11 ` Linus Torvalds
2003-12-15 23:15 ` Roland McGrath
2003-12-15 8:54 ` Arjan van de Ven
2003-12-15 22:55 ` Roland McGrath
2003-12-15 23:06 ` Roland McGrath [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200312152306.hBFN6riq024958@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.org \
--cc=vandrove@vc.cvut.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®