diff options
| author | Alexey Dobriyan <adobriyan@gmail.com> | 2019-07-16 16:26:48 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2019-07-16 19:23:21 -0700 |
| commit | 7dbbade1f285e881119049563ab2a036c96dd9f3 (patch) | |
| tree | 9c45ceb42846a92a8d9d3bbbcdbb26ff21dd1127 /fs/proc | |
| parent | 9af27b28b1da1020e427b626c4967d0206b55100 (diff) | |
| download | linux-7dbbade1f285e881119049563ab2a036c96dd9f3.tar.bz2 | |
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 :-\
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>
Diffstat (limited to 'fs/proc')
0 files changed, 0 insertions, 0 deletions