linux-kernel - Re: [Patch 0/3] posix mqueue namespace (v14)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 26 Jan 2009 15:28:32 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	"Serge E. Hallyn" <serue@...ibm.com>
Cc:	linux-kernel@...r.kernel.org, containers@...ts.osdl.org
Subject: Re: [Patch 0/3] posix mqueue namespace (v14)

On Fri, 16 Jan 2009 20:02:48 -0600
"Serge E. Hallyn" <serue@...ibm.com> wrote:

> IPC namespaces are completely disjoint id->object mappings.
> A task can pass CLONE_NEWIPC to unshare and clone to get
> a new, empty, IPC namespace.  Until now this has supported
> SYSV IPC.
> 
> Most Posix IPC is done in userspace.  The posix mqueue
> support, however, is implemented on top of the mqueue fs.
> 
> This patchset implements multiple mqueue fs instances,
> one per IPC namespace to be precise.
> 
> To create a new ipc namespace with posix mq support, you
> should now:
> 
> 	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.
> After the ipc namespace has exited, you can still
> unlink but no longer create files in that fs (since
> accounting is carried.
> 
> Changelog:
> 	v14: (Jan 16 2009) port to linux-next
> 	v13: (Dec 28 2009)
> 	   1. addressed comments by Dave and Suka
> 	   2. ported Cedric's patch to make posix mq sysctls
> 	      per-namespace
> 
> When convenient, it would be great to see this tested
> in -mm.

hm. Who is going to test it?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/