[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4506D438.6090804@fr.ibm.com>
Date: Tue, 12 Sep 2006 17:37:28 +0200
From: Cedric Le Goater <clg@...ibm.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
CC: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
containers@...ts.osdl.org
Subject: Re: [patch -mm] update mq_notify to use a struct pid
Eric W. Biederman wrote:
[ ... ]
> There is also the case that should not come up with signals where
> we have a pid from a child namespace, that we should also be able to
> compute the pid for.
I don't understand how a signal can come from a child pid namespace ?
> In essence I intend to have a list of pid_namespace, pid_t pairs connected
> to a struct pid that we can look through to find the appropriate pid.
yes, that's the purpose of pid_nr() I guess.
This list would contain in nearly all cases a single pair (current pid
namespace, pid value). It will contain 2 pairs for a task that has unshared
its pid namespace : a pair for the current pid namespace, that needs to
allocated when unshare() is called, and one pair for the ancestor pid
namespace which is already allocated.
Do you see more ?
C.
-
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/
Powered by blists - more mailing lists