Subject: Re: [RFC] [PATCH 00/13] Introduce task_pid api
From: Arjan van de Ven <arjan@infradead.org>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
       "SERGE E. HALLYN [imap]" <serue@us.ibm.com>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       Hubertus Franke <frankeh@watson.ibm.com>, Paul Jackson <pj@sgi.com>
In-Reply-To: <1133977623.24344.31.camel@localhost>
References: <20051114212341.724084000@sergelap>
	 <m1slt5c6d8.fsf@ebiederm.dsl.xmission.com>
	 <1133977623.24344.31.camel@localhost>
Content-Type: text/plain
Date: Wed, 07 Dec 2005 18:55:27 +0100
Message-Id: <1133978128.2869.51.camel@laptopd505.fenrus.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 927
Lines: 23


> > Many of the interesting places that deal with pids and where you
> > want translation are not where the values are read from current->pid,
> > but where the values are passed between functions.  Think about
> > the return value of do_fork.
> 
> Exactly.  The next phase will focus on such places.  Hubertus has some
> stuff working that's probably not ready for LKML, but could certainly be
> shared.
> 

hmm wonder if it's not just a lot simpler to introduce a split in
"kernel pid" and "userspace pid", and have current->pid and
current->user_pid for that.

Using accessor macros doesn't sound like it gains much here.. (but then
I've not seen the full picture and you have)

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