From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cedric Le Goater Subject: Re: namespaces compatibility list Date: Wed, 07 Nov 2007 09:20:58 +0100 Message-ID: <4731756A.3060701@fr.ibm.com> References: <47304729.8000309@openvz.org> <4730640D.9030407@fr.ibm.com> <4730655C.8000306@openvz.org> <47308FDB.4010302@fr.ibm.com> <473091F9.10406@openvz.org> <47309A51.1050607@fr.ibm.com> <47309FAD.90702@openvz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <47309FAD.90702-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Pavel Emelyanov Cc: Linux Containers , "Eric W. Biederman" List-Id: containers.vger.kernel.org Pavel Emelyanov wrote: > Eric W. Biederman wrote: >> Cedric Le Goater writes: >>> right. I think we can address Ulrich concerns first because we have >>> a solution for it (which looks like unsharing all namespaces at once, >>> here comes back the container object story :) >> It doesn't work because we can't create a fresh mount namespace. >> >> We need to create all new mounts (and deny access to the old ones) >> if we want to prevent all possibility of user space goof ups. >> >> While that is easy enough to build an application to do we can't >> easily enforce that in the kernel. Currently this is all >> CAP_SYS_ADMIN so only root can do this anyway. So we can easily >> say don't do that then. >> >> Clone flag consistency checking should only be used to enforce >> cases where the kernel side cannot support correctly. Currently >> the kernel has no problems with the current mix and match possibilities >> short of implementation deficiencies. So I do not see us >> addressing Ulrich's concerns with clone flags. > > ACK :) Since this all is CAP_SYS_ADMIN-ed we can do with just a warning. Fine with me. Let's come back to the document, then. C.