Linux Container Development
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: [RFC patch 0/2] posix mqueue namespace (v11)
Date: Mon, 15 Dec 2008 17:37:47 -0600	[thread overview]
Message-ID: <20081215233747.GA27553@us.ibm.com> (raw)

(Ok I don't know what the actual version number is - it's
high but 11 is probably safe)

Cedric and Nadia took several approaches to making posix
message queues per-namespace.  I ended up mamking some
deep changes so am not retaining their Signed-off-by:s
on this version, but this is definately very much based
on work by both of them.

Patch 2 hopefully explains my approach.  Briefly,

	1. sysv and posix ipc are both under CLONE_NEWIPC
	2. the mqueue sb is per-ipc-namespace

So to create a new ipc namespace, you would

	unshare(CLONE_NEWIPC|CLONE_NEWNS);
	umount /dev/mqueue
	mount -t mqueue mqueue /dev/mqueue

It's perfectly valid to do vfs operations on files
in another ipc_namespace's /dev/mqueue, but any use
of mq_open(3) and friends will act in your own ipc_ns.

thanks,
-serge

             reply	other threads:[~2008-12-15 23:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-15 23:37 Serge E. Hallyn [this message]
     [not found] ` <20081215233747.GA27553-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-12-15 23:38   ` [RFC PATCH 1/2] mqueue ns: move mqueue_mnt into struct ipc_namespace Serge E. Hallyn
2008-12-15 23:38   ` [RFC PATCH 2/2] ipc namespaces: implement support for posix msqueues Serge E. Hallyn
2008-12-16  8:11   ` [RFC patch 0/2] posix mqueue namespace (v11) Cedric Le Goater
     [not found]     ` <4947629D.9040807-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2008-12-16 15:14       ` Serge E. Hallyn

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=20081215233747.GA27553@us.ibm.com \
    --to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.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