From: Benjamin LaHaise <bcrl@redhat.com>
To: David Howells <dhowells@redhat.com>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: thread groups bug?
Date: Thu, 28 Feb 2002 10:59:38 -0500 [thread overview]
Message-ID: <20020228105938.H8011@redhat.com> (raw)
In-Reply-To: <bcrl@redhat.com> <2961.1014910587@warthog.cambridge.redhat.com>
In-Reply-To: <2961.1014910587@warthog.cambridge.redhat.com>; from dhowells@redhat.com on Thu, Feb 28, 2002 at 03:36:27PM +0000
On Thu, Feb 28, 2002 at 03:36:27PM +0000, David Howells wrote:
> > How about: (3) make execve allocate a new thread group id?
>
> It seems that the TGID must also be a valid PID so that signal handling will
> work correctly...
>
> This could be solved by making PIDs independent of processes, but that's
> really not very nice.
Oh, interesting. Note that we already allocate from the pid space for
other things, so it's entirely doable. Another choice would be to simply
disallow the thread group leader from exec'ing. Linux threads traditionally
try to remain as close to process behaviour as possible, and allowing an
individual thread to exec is very useful, so I'm still in favour of
allocating a new tgid.
-ben
--
"A man with a bass just walked in,
and he's putting it down
on the floor."
next prev parent reply other threads:[~2002-02-28 16:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 14:52 thread groups bug? David Howells
2002-02-28 15:18 ` Benjamin LaHaise
2002-02-28 15:36 ` David Howells
2002-02-28 15:59 ` Benjamin LaHaise [this message]
2002-02-28 16:28 ` David Howells
-- strict thread matches above, loose matches on Subject: below --
2002-02-28 15:09 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
2002-03-01 16:38 ` David Howells
2002-03-01 17:01 ` Martin Dalecki
2002-03-01 17:05 ` Dave McCracken
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=20020228105938.H8011@redhat.com \
--to=bcrl@redhat.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