From: ebiederm@xmission.com (Eric W. Biederman)
To: Cedric Le Goater <clg@fr.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Containers <containers@lists.osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pavel Emelianov <xemul@openvz.org>
Subject: Re: [patch -mm 2/4] mqueue namespace : add unshare support
Date: Thu, 29 Nov 2007 08:03:44 -0700 [thread overview]
Message-ID: <m1y7chccvj.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20071128164349.196734045@fr.ibm.com>> (Cedric Le Goater's message of "Wed, 28 Nov 2007 17:37:30 +0100")
Cedric Le Goater <clg@fr.ibm.com> writes:
> From: Cedric Le Goater <clg@fr.ibm.com>
>
> This patch includes the mqueue namespace in the nsproxy object. It
> also adds the support of unshare() and clone() with a new clone flag
> CLONE_NEWMQ (1 bit left in the clone flags !)
>
> CLONE_NEWMQ is required to be cloned or unshared along with CLONE_NEWNS.
> This is to make sure that no user mounts of the internal mqueue fs
> are left behind when the last task exits.
Sounds reasonable. It would be cool if we didn't have to do this.
(Why isn't the mqueue fs not MS_NOUSER?) Ah well.
I'm not certain about requiring CLONE_NEWNS but it looks to be
ugly if we try and work it the other way.
> It's totally harmless for the moment because the current code still
> uses the default mqueue namespace object 'init_mq_ns'
I don't believe the harmless part. Creating new objects should really
come after we have the code to really make them work. In some sense
the next patch which makes this work causes ABI breakage. Closely
packed together it doesn't matter but...
Eric
next prev parent reply other threads:[~2007-11-29 15:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071128163728.177495768@fr.ibm.com>
2007-11-28 16:37 ` [patch -mm 1/4] mqueue namespace : add struct mq_namespace Cedric Le Goater
2007-11-28 16:37 ` [patch -mm 2/4] mqueue namespace : add unshare support Cedric Le Goater
2007-11-28 16:37 ` [patch -mm 3/4] mqueue namespace : enable the mqueue namespace Cedric Le Goater
2007-11-28 16:37 ` [patch -mm 4/4] mqueue namespace: adapt sysctl Cedric Le Goater
[not found] ` <20071128163728.177495768-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
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
[not found] ` <474DA61B.5030301-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-11-29 10:28 ` Cedric Le Goater
2007-11-29 10:52 ` Andrew Morton
2007-11-29 13:57 ` Serge E. Hallyn
[not found] ` <474E944C.4020809-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-11-29 20:14 ` Oren Laadan
2007-11-29 21:49 ` Eric W. Biederman
2007-11-29 15:03 ` Eric W. Biederman [this message]
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=m1y7chccvj.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=clg@fr.ibm.com \
--cc=containers@lists.osdl.org \
--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