summaryrefslogtreecommitdiffstats
path: root/kernel
diff options
context:
space:
mode:
authorAl Viro <viro@zeniv.linux.org.uk>2018-08-09 10:15:54 -0400
committerAl Viro <viro@zeniv.linux.org.uk>2018-08-09 18:07:15 -0400
commit4c0d7cd5c8416b1ef41534d19163cb07ffaa03ab (patch)
tree1271fc0ec0ee812900750b246c90afd807efabac /kernel
parent119e1ef80ecfe0d1deb6378d4ab41f5b71519de1 (diff)
downloadlinux-4c0d7cd5c8416b1ef41534d19163cb07ffaa03ab.tar.bz2
make sure that __dentry_kill() always invalidates d_seq, unhashed or not
RCU pathwalk relies upon the assumption that anything that changes ->d_inode of a dentry will invalidate its ->d_seq. That's almost true - the one exception is that the final dput() of already unhashed dentry does *not* touch ->d_seq at all. Unhashing does, though, so for anything we'd found by RCU dcache lookup we are fine. Unfortunately, we can *start* with an unhashed dentry or jump into it. We could try and be careful in the (few) places where that could happen. Or we could just make the final dput() invalidate the damn thing, unhashed or not. The latter is much simpler and easier to backport, so let's do it that way. Reported-by: "Dae R. Jeong" <threeearcat@gmail.com> Cc: stable@vger.kernel.org Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions