diff options
| author | Al Viro <viro@zeniv.linux.org.uk> | 2012-09-21 08:19:02 -0400 |
|---|---|---|
| committer | Ziyan <jaraidaniel@gmail.com> | 2016-03-11 16:08:10 +0100 |
| commit | 79a251bb57e4ff32e397eb6d78a3285ded7b9d7b (patch) | |
| tree | 9264e6995d845659f017aa324b5effb61691d98b /security/tomoyo | |
| parent | 46b5384cc5112152a94c2fd03cf727dad8dbf330 (diff) | |
| download | kernel_samsung_espresso10-79a251bb57e4ff32e397eb6d78a3285ded7b9d7b.zip kernel_samsung_espresso10-79a251bb57e4ff32e397eb6d78a3285ded7b9d7b.tar.gz kernel_samsung_espresso10-79a251bb57e4ff32e397eb6d78a3285ded7b9d7b.tar.bz2 | |
do_add_mount()/umount -l races
normally we deal with lock_mount()/umount races by checking that
mountpoint to be is still in our namespace after lock_mount() has
been done. However, do_add_mount() skips that check when called
with MNT_SHRINKABLE in flags (i.e. from finish_automount()). The
reason is that ->mnt_ns may be a temporary namespace created exactly
to contain automounts a-la NFS4 referral handling. It's not the
namespace of the caller, though, so check_mnt() would fail here.
We still need to check that ->mnt_ns is non-NULL in that case,
though.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
(cherry picked from commit 156cacb1d0d36b0d0582d9e798e58e0044f516b3)
Diffstat (limited to 'security/tomoyo')
0 files changed, 0 insertions, 0 deletions