Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S293183AbSB1Pin>; Thu, 28 Feb 2002 10:38:43 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S293432AbSB1PiR>; Thu, 28 Feb 2002 10:38:17 -0500
Received: from dell-paw-3.cambridge.redhat.com ([195.224.55.237]:35579 "HELO
	executor.cambridge.redhat.com") by vger.kernel.org with SMTP
	id <S293423AbSB1Pg3>; Thu, 28 Feb 2002 10:36:29 -0500
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: thread groups bug? 
In-Reply-To: Message from Benjamin LaHaise <bcrl@redhat.com> 
   of "Thu, 28 Feb 2002 10:18:00 EST." <20020228101800.F8011@redhat.com> 
User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3
 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.1
 (i386-redhat-linux-gnu) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 28 Feb 2002 15:36:27 +0000
Message-ID: <2961.1014910587@warthog.cambridge.redhat.com>
From: David Howells <dhowells@redhat.com>
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org


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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/