[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50A9F7DE.60807@cn.fujitsu.com>
Date: Mon, 19 Nov 2012 17:11:58 +0800
From: Gao feng <gaofeng@...fujitsu.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
CC: Linux Containers <containers@...ts.linux-foundation.org>,
linux-kernel@...r.kernel.org, Oleg Nesterov <oleg@...sign.ru>,
Serge Hallyn <serge@...lyn.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 09/11] pidns: Add setns support
于 2012年11月17日 00:35, Eric W. Biederman 写道:
> From: "Eric W. Biederman" <ebiederm@...ssion.com>
>
> - Pid namespaces are designed to be inescapable so verify that the
> passed in pid namespace is a child of the currently active
> pid namespace or the currently active pid namespace itself.
>
> Allowing the currently active pid namespace is important so
> the effects of an earlier setns can be cancelled.
>
> Signed-off-by: Eric W. Biederman <ebiederm@...ssion.com>
> ---
Hi Eric
I noticed that,after we call setns to change task's pidns to container A's pidns.
we can't see this task in container A's proc filesystem.
Is this what we expected?
Thanks
Gao
--
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