diff options
author | Eric W. Biederman <ebiederm@xmission.com> | 2015-08-15 20:27:13 -0500 |
---|---|---|
committer | Al Viro <viro@zeniv.linux.org.uk> | 2015-08-21 03:20:10 -0400 |
commit | 397d425dc26da728396e66d392d5dcb8dac30c37 (patch) | |
tree | 14a2ec6d000fa7b5b45d91bb62d2f89fc11d28b5 /arch/Kconfig | |
parent | a03e283bf5c3d4851b4998122196ce9f849e6dfb (diff) | |
download | linux-397d425dc26da728396e66d392d5dcb8dac30c37.tar.gz linux-397d425dc26da728396e66d392d5dcb8dac30c37.tar.bz2 linux-397d425dc26da728396e66d392d5dcb8dac30c37.zip |
vfs: Test for and handle paths that are unreachable from their mnt_root
In rare cases a directory can be renamed out from under a bind mount.
In those cases without special handling it becomes possible to walk up
the directory tree to the root dentry of the filesystem and down
from the root dentry to every other file or directory on the filesystem.
Like division by zero .. from an unconnected path can not be given
a useful semantic as there is no predicting at which path component
the code will realize it is unconnected. We certainly can not match
the current behavior as the current behavior is a security hole.
Therefore when encounting .. when following an unconnected path
return -ENOENT.
- Add a function path_connected to verify path->dentry is reachable
from path->mnt.mnt_root. AKA to validate that rename did not do
something nasty to the bind mount.
To avoid races path_connected must be called after following a path
component to it's next path component.
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'arch/Kconfig')
0 files changed, 0 insertions, 0 deletions