RFC posix mqueue namespace (v11)
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | mqueue ns: move mqueue_mnt into struct ipc_namespaceinclude/ init/ ipc/ +4 more | +131 | 0 replies | |
| 2/2 | ipc namespaces: implement support for posix msqueuesinclude/ ipc/ ipc/ +2 more | +154 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC patch 0/2] posix mqueue namespace (v11)
(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