From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Serge E. Hallyn" Subject: Re: [RFC][PATCH] ns: Syscalls for better namespace sharing control. Date: Mon, 8 Mar 2010 15:49:45 -0600 Message-ID: <20100308214945.GA26617@us.ibm.com> References: <4B92C886.9020507@free.fr> <4B952BBE.6070507@free.fr> <4B9556A9.60206@free.fr> <4B95611C.5060403@free.fr> <4B956852.7050804@free.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Daniel Lezcano , Pavel Emelyanov , Sukadev Bhattiprolu , Linux Netdev List , containers@lists.linux-foundation.org, Netfilter Development Mailinglist , Ben Greear To: "Eric W. Biederman" Return-path: Received: from e3.ny.us.ibm.com ([32.97.182.143]:47125 "EHLO e3.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755810Ab0CHVts (ORCPT ); Mon, 8 Mar 2010 16:49:48 -0500 Content-Disposition: inline In-Reply-To: Sender: netfilter-devel-owner@vger.kernel.org List-ID: Quoting Eric W. Biederman (ebiederm@xmission.com): > Daniel Lezcano writes: > I guess my meaning is I was expecting. > child = fork(); > if (child == 0) { > execve(...); > } > waitpid(child); > > This puts /bin/sh in the container as well. > > I'm not certain about the /proc/self thing I have never encountered that. > But I guess if your pid is outside of the pid namespace of that instance > of proc /proc/self will be a broken symlink. > > Eric Hmm, worse than a broken symlink, will it be a wrong symlink if just the right pid is created in the container? -serge