summaryrefslogtreecommitdiffstats
path: root/fs/btrfs/tree-log.c
diff options
context:
space:
mode:
authorAndrey Ulanov <andreyu@google.com>2016-04-15 23:24:41 +0200
committerAl Viro <viro@zeniv.linux.org.uk>2016-07-01 05:28:30 +0200
commite06b933e6ded42384164d28a2060b7f89243b895 (patch)
tree5dfb0149aec8be222d613391fd1e49c791d6485f /fs/btrfs/tree-log.c
parent9p: use file_dentry() (diff)
downloadlinux-e06b933e6ded42384164d28a2060b7f89243b895.tar.xz
linux-e06b933e6ded42384164d28a2060b7f89243b895.zip
namespace: update event counter when umounting a deleted dentry
- m_start() in fs/namespace.c expects that ns->event is incremented each time a mount added or removed from ns->list. - umount_tree() removes items from the list but does not increment event counter, expecting that it's done before the function is called. - There are some codepaths that call umount_tree() without updating "event" counter. e.g. from __detach_mounts(). - When this happens m_start may reuse a cached mount structure that no longer belongs to ns->list (i.e. use after free which usually leads to infinite loop). This change fixes the above problem by incrementing global event counter before invoking umount_tree(). Change-Id: I622c8e84dcb9fb63542372c5dbf0178ee86bb589 Cc: stable@vger.kernel.org Signed-off-by: Andrey Ulanov <andreyu@google.com> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'fs/btrfs/tree-log.c')
0 files changed, 0 insertions, 0 deletions