proc: test /proc/sysvipc vs setns(CLONE_NEWIPC)
Subsystems (2)
PATCH 1/1 proc: test /proc/sysvipc vs setns(CLONE_NEWIPC)
I thought that /proc/sysvipc has the same bug as /proc/net
commit 1fde6f21d90f8ba5da3cb9c54ca991ed72696c43 proc: fix /proc/net/* after setns(2)
However, it doesn't! /proc/sysvipc files do
get_ipc_ns(current->nsproxy->ipc_ns);
in their open() hook and avoid the problem.
Keep the test, maybe /proc/sysvipc will become broken someday :-\
Signed-off-by Alexey Dobriyan <[email protected]>
---
tools/testing/selftests/proc/.gitignore | 1 tools/testing/selftests/proc/Makefile | 1 tools/testing/selftests/proc/setns-sysvipc.c | 133 +++++++++++++++++++++++++++ 3 files changed, 135 insertions(+)
tools/testing/selftests/proc/.gitignore +1 -0
@@ -12,4 +12,5 @@ /read /self /setns-dcache +/setns-sysvipc /thread-self
tools/testing/selftests/proc/Makefile +1 -0
@@ -17,6 +17,7 @@ TEST_GEN_PROGS += proc-uptime-002 TEST_GEN_PROGS += read TEST_GEN_PROGS += self TEST_GEN_PROGS += setns-dcache +TEST_GEN_PROGS += setns-sysvipc TEST_GEN_PROGS += thread-self include ../lib.mk
new file mode 100644
tools/testing/selftests/proc/setns-sysvipc.c new file +133 -0
133 lines not on this page · raw message