From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755204AbZFPTzU (ORCPT ); Tue, 16 Jun 2009 15:55:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752889AbZFPTzJ (ORCPT ); Tue, 16 Jun 2009 15:55:09 -0400 Received: from www84.your-server.de ([213.133.104.84]:54302 "EHLO www84.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751995AbZFPTzI (ORCPT ); Tue, 16 Jun 2009 15:55:08 -0400 Subject: Re: [RFC] set the thread name From: Stefani Seibold To: Bert Wesarg Cc: linux-kernel , linux-mm , Andrew Morton In-Reply-To: <36ca99e90906161214u6624014q3f3dc4e234bdf772@mail.gmail.com> References: <1245177592.14543.1.camel@wall-e> <36ca99e90906161214u6624014q3f3dc4e234bdf772@mail.gmail.com> Content-Type: text/plain Date: Tue, 16 Jun 2009 21:54:51 +0200 Message-Id: <1245182091.16466.9.camel@wall-e> Mime-Version: 1.0 X-Mailer: Evolution 2.26.2 Content-Transfer-Encoding: 7bit X-Authenticated-Sender: stefani@seibold.net Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Dienstag, den 16.06.2009, 21:14 +0200 schrieb Bert Wesarg: > Hi, > > On Tue, Jun 16, 2009 at 20:39, Stefani Seibold wrote: > > Currently it is not easy to identify a thread in linux, because there is > > no thread name like in some other OS. > > > > If there were are thread name then we could extend a kernel segv message > > and the /proc//task//... entries by a TName value like this: > prctl(PR_SET_NAME, ...) works perfectly here. > I checked it now a little bit more. It is true it works, but if i do a segv access inside a thread a get the kernel message like: task 09[17395]: segfault at 0 ip 08048612 sp b363c370 error 6 in a.out[8048000+1000] So the current implementation is not exactly what i expect. I would prefer my solution to replace every access thread_struct->comm to task_struct->group_leader->comm to have the right behavior. The new system call is obsolete, it is still there.