linux-kernel - Re: [PATCH 3/5] Use task_pid() to find leader's pid

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20070717134415.GA226@tv-sign.ru>
Date:	Tue, 17 Jul 2007 17:44:15 +0400
From:	Oleg Nesterov <oleg@...sign.ru>
To:	sukadev@...ibm.com
Cc:	Andrew Morton <akpm@...l.org>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Cedric Le Goater <clg@...ibm.com>,
	Dave Hansen <haveblue@...ibm.com>,
	Serge Hallyn <serue@...ibm.com>,
	Herbert Poetzel <herbert@...hfloor.at>,
	Pavel Emelianov <xemul@...nvz.org>,
	Linux Containers <containers@...ts.osdl.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/5] Use task_pid() to find leader's pid

On 07/16, sukadev@...ibm.com wrote:
>
> Oleg Nesterov [oleg@...sign.ru] wrote:
> | 
> | Stupid question: why do we need to put the pid namespace into the struct
> | pid? Isn't it better if the user of the struct pid should know its ns?
> | For example, if /proc does put_pid(), that pid should be from the active
> | namespace.
> 
> Not sure I fully understand this. A process, and by extension its 'struct
> pid' is visible in multiple namespaces and we maintain this list of
> namespaces in each 'struct pid'.
> 
> Are you suggesting having a pid_namespace with a list of all 'struct pids'
> that are visible in it ?

I thought that the plan is: if the task is visible in some namespace, it has
a separate pid_t in that namespace.

OK, the question was relly stupid, please ignore. I'll wait for other patches
to understand what's going on.

Oleg.

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