aboutsummaryrefslogtreecommitdiffstats
path: root/Kconfig
diff options
context:
space:
mode:
authorEric W. Biederman <ebiederm@xmission.com>2015-08-15 20:27:13 -0500
committerBen Hutchings <ben@decadent.org.uk>2015-10-13 03:46:04 +0100
commit6d84ade2c8242ab83fbc5bacb66eb81a8d1ca6db (patch)
tree406e247bf5400b4fa331ab6fe9f7e668c880698b /Kconfig
parent722632af3c2b4828e79f143e356489c6761035ec (diff)
downloadkernel_samsung_smdk4412-6d84ade2c8242ab83fbc5bacb66eb81a8d1ca6db.zip
kernel_samsung_smdk4412-6d84ade2c8242ab83fbc5bacb66eb81a8d1ca6db.tar.gz
kernel_samsung_smdk4412-6d84ade2c8242ab83fbc5bacb66eb81a8d1ca6db.tar.bz2
vfs: Test for and handle paths that are unreachable from their mnt_root
commit 397d425dc26da728396e66d392d5dcb8dac30c37 upstream. 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> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
Diffstat (limited to 'Kconfig')
0 files changed, 0 insertions, 0 deletions