All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: thread groups bug?
Date: Thu, 28 Feb 2002 15:36:27 +0000	[thread overview]
Message-ID: <2961.1014910587@warthog.cambridge.redhat.com> (raw)
In-Reply-To: Message from Benjamin LaHaise <bcrl@redhat.com>  of "Thu, 28 Feb 2002 10:18:00 EST." <20020228101800.F8011@redhat.com>


Benjamin LaHaise <bcrl@redhat.com> wrote:
> On Thu, Feb 28, 2002 at 02:52:36PM +0000, David Howells wrote:
> > 
> > If the master thread of a thread group (PID==TGID) performs an execve()
> > then it is possible to end up with two or more thread groups with the same
> > TGID.
> 
> 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.

David

  reply	other threads:[~2002-02-28 15:38 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 [this message]
2002-02-28 15:59     ` Benjamin LaHaise
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=2961.1014910587@warthog.cambridge.redhat.com \
    --to=dhowells@redhat.com \
    --cc=bcrl@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.