From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Darren Hart <dvhltc@us.ibm.com>
Subject: Re: [RFC][PATCH] Add prctl to set sibling thread names
Cc: kosaki.motohiro@jp.fujitsu.com, Andrew Morton <akpm@linux-foundation.org>,
       john stultz <johnstul@us.ibm.com>,
       Arjan van de Ven <arjan@infradead.org>,
       Andi Kleen <andi@firstfloor.org>, lkml <linux-kernel@vger.kernel.org>,
       Mike Fulton <fultonm@ca.ibm.com>, Sean Foley <Sean_Foley@ca.ibm.com>
In-Reply-To: <4AF25FFB.5020700@us.ibm.com>
References: <20091105112303.208A.A69D9226@jp.fujitsu.com> <4AF25FFB.5020700@us.ibm.com>
Message-Id: <20091105141953.2090.A69D9226@jp.fujitsu.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Thu,  5 Nov 2009 14:22:05 +0900 (JST)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 843
Lines: 26

> KOSAKI Motohiro wrote:
> 
> > John, I'd prefer to suggested another design.
> > How about this?
> > 
> > 1. remove pid argument from prctl
> > 2. cancel pthread_setname_np()
> > 3. instead, create pthread_attr_setname_np()
> > 4. pthread_create() change own thread name by pthread_attr.
> > 
> > It avoid many racy problem automatically.
> 
> Perhaps, but it also greatly reduces the flexibility of the 
> implementation by restricting name changes to create time.

Hm.
if your program really need to change another thread name, can you please tell us
why it is necessary and when it is used?


--
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/