From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Cedric Le Goater <clg@fr.ibm.com>,
Linux Containers <containers@lists.osdl.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pavel Emelyanov <xemul@openvz.org>
Subject: Re: [patch -mm 2/4] mqueue namespace : add unshare support
Date: Thu, 29 Nov 2007 07:57:28 -0600 [thread overview]
Message-ID: <20071129135727.GA3343@sergelap.austin.ibm.com> (raw)
In-Reply-To: <20071129025246.a0d03eef.akpm@linux-foundation.org>
Quoting Andrew Morton (akpm@linux-foundation.org):
> On Thu, 29 Nov 2007 11:28:28 +0100 Cedric Le Goater <clg@fr.ibm.com> wrote:
>
> > >> Index: 2.6.24-rc3-mm2/include/linux/sched.h
> > >> ===================================================================
> > >> --- 2.6.24-rc3-mm2.orig/include/linux/sched.h
> > >> +++ 2.6.24-rc3-mm2/include/linux/sched.h
> > >> @@ -27,6 +27,7 @@
> > >> #define CLONE_NEWUSER 0x10000000 /* New user namespace */
> > >> #define CLONE_NEWPID 0x20000000 /* New pid namespace */
> > >> #define CLONE_NEWNET 0x40000000 /* New network namespace */
> > >> +#define CLONE_NEWMQ 0x80000000 /* New posix mqueue namespace */
> > >
> > > That's it :) We've run out of clone flags on 32-bit platforms :(
> >
> > yes.
> >
> > I have been giving some thoughts to a clone2() to extend the flags
>
> There appears to be little alternative.
Just thinking aloud, but
given the concerns with the safety and sanity of unsharing only partial
namespaces, and before much userspace is depending on any of
CLONE_NEWUTS,CLONE_NEWIPC,CLONE_NEWUSER,CLONE_NEWNET,CLONE_NEWMQUEUE
maybe we should have traditional clone only support CLONE_NEWNS (since
it's the most useful on its own) and CLONE_NEWCONTAINER, where
CLONE_NEWCONTAINER always unshares all the namespaces we know about.
Then clone2 can allow more finegrained choice of namespaces. It takes
the exact same clone_flags as clone(), but instead of parent_tidptr
and child_tidptr args it has a ns_unshare flag which specifies which
namespaces to unshare.
-serge
> > but
> > andrew is preparing to recycle CLONE_DETACHED and CLONE_STOPPED for
> > 2.6.26. Some we might have some more time in front of us.
>
> CLONE_DETACHED proved to be in use. There are no reports of anyone using
> CLONE_STOPPED though.
>
> _______________________________________________
> Containers mailing list
> Containers@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/containers
next prev parent reply other threads:[~2007-11-29 13:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071128163728.177495768@fr.ibm.com>
2007-11-28 17:28 ` [patch -mm 0/4] mqueue namespace Pavel Emelyanov
2007-11-29 9:52 ` Cedric Le Goater
[not found] ` <20071128164349.196734045@fr.ibm.com>
2007-11-28 17:32 ` [patch -mm 2/4] mqueue namespace : add unshare support Pavel Emelyanov
2007-11-29 10:28 ` Cedric Le Goater
2007-11-29 10:28 ` Cedric Le Goater
2007-11-29 10:52 ` Andrew Morton
2007-11-29 13:57 ` Serge E. Hallyn [this message]
2007-11-29 20:14 ` Oren Laadan
2007-11-29 21:49 ` Eric W. Biederman
2007-11-29 15:03 ` Eric W. Biederman
2008-06-20 3:00 ` [patch -mm 0/4] mqueue namespace Eric W. Biederman
2008-06-20 3:39 ` Eric W. Biederman
2008-06-20 14:53 ` Serge E. Hallyn
2008-08-29 9:46 ` Cedric Le Goater
2008-06-20 14:50 ` Serge E. Hallyn
2008-06-20 19:11 ` Eric W. Biederman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071129135727.GA3343@sergelap.austin.ibm.com \
--to=serue@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=clg@fr.ibm.com \
--cc=containers@lists.osdl.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xemul@openvz.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®