From: "Serge E. Hallyn" <serue@us.ibm.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>,
Dave Hansen <haveblue@us.ibm.com>
Cc: Cedric Le Goater <clg@fr.ibm.com>,
Linux Containers <containers@lists.osdl.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pavel Emelianov <xemul@openvz.org>
Subject: Re: [patch -mm 0/4] mqueue namespace
Date: Fri, 20 Jun 2008 09:50:31 -0500 [thread overview]
Message-ID: <20080620145031.GA30800@us.ibm.com> (raw)
In-Reply-To: <m11w2syfmk.fsf@frodo.ebiederm.org>
Quoting Eric W. Biederman (ebiederm@xmission.com):
> Cedric Le Goater <clg@fr.ibm.com> writes:
>
> > Hello !
> >
> > Here's a small patchset introducing a new namespace for POSIX
> > message queues.
> >
> > Nothing really complex a part from the mqueue filesystem which
> > needed some special care
>
> This looks stalled.
It actually isn't really - Cedric had resent it a few weeks ago but had
troubles with the mail server so it never hit the lists. I think Dave
made a few more changes from there and was getting ready to resend
again. Dave?
> I have a brainstorm that might takes a totally
> different perspective on things.
>
> The only reason we don't just allow multiple mounts of mqueuefs to
> solve this problem is because there is a kernel syscall on the path.
>
> If we just hard coded a mount point into the kernel and required user
> space to always mount mqueuefs there the problem would be solved.
>
> hard coding a mount point is unfortunately violates the unix rule
> of separating mechanism and policy.
>
> One way to fix that is to add a hidden directory to the mnt namespace.
> Where magic in kernel filesystems can be mounted. Only visible
> with a magic openat flag. Then:
>
> fd = openat(AT_FDKERN, ".", O_DIRECTORY)
> fchdir(fd);
> umount("./mqueue", MNT_DETACH);
> mount(("none", "./mqueue", "mqueue", 0, NULL);
>
> Would unshare the mqueue namespace.
>
> Implemented for plan9 this would solve a problem of how do you get
> access to all of it's special filesystems. As only bind mounts
> and remote filesystem mounts are available. For linux thinking about
> it might shake the conversation up a bit.
It is unfortunate that two actions are needed to properly complete the
unshare, and we had definately talked about just using the mount before.
I forget why we decided it wasn't practical, so maybe what you describe
solves it...
But at least the current patch reuses CLONE_NEWIPC for posix ipc, which
also seems to make sense.
-serge
next prev parent reply other threads:[~2008-06-20 14:50 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
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 [this message]
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=20080620145031.GA30800@us.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=haveblue@us.ibm.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;
as well as URLs for NNTP newsgroup(s).