From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cedric Le Goater Subject: Re: namespaces compatibility list Date: Tue, 06 Nov 2007 17:01:31 +0100 Message-ID: <47308FDB.4010302@fr.ibm.com> References: <47304729.8000309@openvz.org> <4730640D.9030407@fr.ibm.com> <4730655C.8000306@openvz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4730655C.8000306-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: > Cedric Le Goater wrote: >> Pavel Emelyanov wrote: >>> Hi guys! >>> >>> As you might have seen, recently there was some spontaneous >>> discussion about the namespaces-working-together problems. >>> >>> Ted T'so proposed to create some document that describes what >>> problems user may have when he/she creates some new namespace, >>> but keeps others shared. I like this idea, so here's the draft >>> with the problems I currently have in mind and can describe >>> somewhat audibly - the "namespaces compatibility list". >> that compatibility list could be encoded in the way we check >> the clone flags in copy_process() and unshare(). It would >> also be good to have it as a comment somewhere in kernel/fork.c > > How can we insure, that a new task will not share the files > with its parent to address the PID namespaces vs VFS namespaces > interaction? There's no way to do it. We can only keep them in > one IPC namespace... ? I'm not sure I understand you. C.