Alexey Dobriyan 7dbbade1f2 proc: test /proc/sysvipc vs setns(CLONE_NEWIPC) ... I thought that /proc/sysvipc has the same bug as /proc/net commit 1fde6f21d9 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 :-\ Link: http://lkml.kernel.org/r/20190706180146.GA21015@avx2 Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>		2019-07-16 19:23:21 -07:00
..
.gitignore
config
fd-001-lookup.c
fd-002-posix-eq.c
fd-003-kthread.c
Makefile
proc-loadavg-001.c
proc-pid-vm.c
proc-self-map-files-001.c
proc-self-map-files-002.c
proc-self-syscall.c
proc-self-wchan.c
proc-uptime-001.c
proc-uptime-002.c
proc-uptime.h
proc.h
read.c
self.c
setns-dcache.c
setns-sysvipc.c
thread-self.c