diff options
author | Eric W. Biederman <ebiederm@xmission.com> | 2015-01-03 05:39:35 -0600 |
---|---|---|
committer | Eric W. Biederman <ebiederm@xmission.com> | 2015-04-02 20:34:19 -0500 |
commit | 5d88457eb5b86b475422dc882f089203faaeedb5 (patch) | |
tree | 19d4a52f225092dfa2875dcb073d129151e910cf /fs/namespace.c | |
parent | 411a938b5abc9cb126c41cccf5975ae464fe0f3e (diff) |
mnt: On an unmount propagate clearing of MNT_LOCKED
A prerequisite of calling umount_tree is that the point where the tree
is mounted at is valid to unmount.
If we are propagating the effect of the unmount clear MNT_LOCKED in
every instance where the same filesystem is mounted on the same
mountpoint in the mount tree, as we know (by virtue of the fact
that umount_tree was called) that it is safe to reveal what
is at that mountpoint.
Cc: stable@vger.kernel.org
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Diffstat (limited to 'fs/namespace.c')
-rw-r--r-- | fs/namespace.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/fs/namespace.c b/fs/namespace.c index 083e3401a808..2b12b7a9455d 100644 --- a/fs/namespace.c +++ b/fs/namespace.c @@ -1333,6 +1333,9 @@ static void umount_tree(struct mount *mnt, enum umount_tree_flags how) LIST_HEAD(tmp_list); struct mount *p; + if (how & UMOUNT_PROPAGATE) + propagate_mount_unlock(mnt); + /* Gather the mounts to umount */ for (p = mnt; p; p = next_mnt(p, mnt)) { p->mnt.mnt_flags |= MNT_UMOUNT; |