[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87ppqdjg6f.fsf@tw-ebiederman.twitter.com>
Date: Wed, 06 Nov 2013 14:53:12 -0800
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Serge Hallyn <serge.hallyn@...ntu.com>
Cc: Oleg Nesterov <oleg@...hat.com>,
Andy Lutomirski <luto@...capital.net>,
Brad Spengler <spender@...ecurity.net>,
Christian Seiler <christian@...kd.de>,
lkml <linux-kernel@...r.kernel.org>,
Andy Whitcroft <apw@...onical.com>,
Lxc development list <lxc-devel@...ts.sourceforge.net>
Subject: Re: CLONE_PARENT after setns(CLONE_NEWPID)
Serge Hallyn <serge.hallyn@...ntu.com> writes:
> So apart from peers seeing the new task as having pid 0, and
> sigchild going to the grandparent, are there any other side
> effects? Is ptrace an issue? (I took a quick look but it
> doesn't seem like it)
There is nothing new the pid namespace adds to the pid namespace case.
Eric
--
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