From: Dave McCracken <dmccr@us.ibm.com>
To: Linus Torvalds <torvalds@transmeta.com>,
David Howells <dhowells@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: thread groups bug?
Date: Fri, 01 Mar 2002 10:24:30 -0600 [thread overview]
Message-ID: <36310000.1014999870@baldur> (raw)
In-Reply-To: <Pine.LNX.4.33.0202281616510.31454-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0202281616510.31454-100000@penguin.transmeta.com>
--On Thursday, February 28, 2002 16:20:21 -0800 Linus Torvalds
<torvalds@transmeta.com> wrote:
> Maybe killing the other threads on execve _is_ the right thing after all,
> if that also gives us POSIX behaviour.
>
> Who actually maintains the pthread library? I don't think they use
> CLONE_THREAD at all yet, right?
As far as I know, Linuxthreads is maintained by Ullrich Drepper, and it
doesn't use CLONE_THREAD. IBM's NGPT pthread library does use
CLONE_THREAD, and I'm the one who's handling kernel issues related to it.
I could code up something that does a 'kill the thread group on execve' if
you'd like me to.
Dave McCracken
======================================================================
Dave McCracken IBM Linux Base Kernel Team 1-512-838-3059
dmccr@us.ibm.com T/L 678-3059
next prev parent reply other threads:[~2002-03-01 16:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 15:09 thread groups bug? David Howells
2002-02-28 17:16 ` Linus Torvalds
2002-02-28 21:57 ` David Howells
2002-03-01 0:20 ` Linus Torvalds
2002-03-01 16:24 ` Dave McCracken [this message]
2002-03-01 16:38 ` David Howells
2002-03-01 17:01 ` Martin Dalecki
2002-03-01 17:05 ` Dave McCracken
-- strict thread matches above, loose matches on Subject: below --
2002-02-28 14:52 David Howells
2002-02-28 15:18 ` Benjamin LaHaise
2002-02-28 15:36 ` David Howells
2002-02-28 15:59 ` Benjamin LaHaise
2002-02-28 16:28 ` David Howells
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=36310000.1014999870@baldur \
--to=dmccr@us.ibm.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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