diff options
author | Eric W. Biederman <ebiederm@xmission.com> | 2015-05-14 04:51:09 +0300 |
---|---|---|
committer | Eric W. Biederman <ebiederm@xmission.com> | 2015-07-01 18:36:49 +0300 |
commit | 7236c85e1be51a9e25ba0f6e087a66ca89605a49 (patch) | |
tree | dea4b45dab48f7485e977364adbbc95868f5f096 /fs/dcache.c | |
parent | f9bb48825a6b5d02f4cabcc78967c75db903dcdc (diff) | |
download | linux-7236c85e1be51a9e25ba0f6e087a66ca89605a49.tar.xz |
mnt: Update fs_fully_visible to test for permanently empty directories
fs_fully_visible attempts to make fresh mounts of proc and sysfs give
the mounter no more access to proc and sysfs than if they could have
by creating a bind mount. One aspect of proc and sysfs that makes
this particularly tricky is that there are other filesystems that
typically mount on top of proc and sysfs. As those filesystems are
mounted on empty directories in practice it is safe to ignore them.
However testing to ensure filesystems are mounted on empty directories
has not been something the in kernel data structures have supported so
the current test for an empty directory which checks to see
if nlink <= 2 is a bit lacking.
proc and sysfs have recently been modified to use the new empty_dir
infrastructure to create all of their dedicated mount points. Instead
of testing for S_ISDIR(inode->i_mode) && i_nlink <= 2 to see if a
directory is empty, test for is_empty_dir_inode(inode). That small
change guaranteess mounts found on proc and sysfs really are safe to
ignore, because the directories are not only empty but nothing can
ever be added to them. This guarantees there is nothing to worry
about when mounting proc and sysfs.
Cc: stable@vger.kernel.org
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Diffstat (limited to 'fs/dcache.c')
0 files changed, 0 insertions, 0 deletions