summaryrefslogtreecommitdiffstats
path: root/kernel
diff options
context:
space:
mode:
authorAl Viro <viro@zeniv.linux.org.uk>2014-08-10 09:44:55 +0200
committerAl Viro <viro@zeniv.linux.org.uk>2014-08-11 18:28:10 +0200
commit12a5b5294cb1896e9a3c9fca8ff5a7e3def4e8c6 (patch)
tree9a3780d90c484e1a18e37b980d3d6cf2ac766711 /kernel
parent__generic_file_write_iter(): fix handling of sync error after DIO (diff)
downloadlinux-12a5b5294cb1896e9a3c9fca8ff5a7e3def4e8c6.tar.xz
linux-12a5b5294cb1896e9a3c9fca8ff5a7e3def4e8c6.zip
fix copy_tree() regression
Since 3.14 we had copy_tree() get the shadowing wrong - if we had one vfsmount shadowing another (i.e. if A is a slave of B, C is mounted on A/foo, then D got mounted on B/foo creating D' on A/foo shadowed by C), copy_tree() of A would make a copy of D' shadow the the copy of C, not the other way around. It's easy to fix, fortunately - just make sure that mount follows the one that shadows it in mnt_child as well as in mnt_hash, and when copy_tree() decides to attach a new mount, check if the last child it has added to the same parent should be shadowing the new one. And if it should, just use the same logics commit_tree() has - put the new mount into the hash and children lists right after the one that should shadow it. Cc: stable@vger.kernel.org [3.14 and later] Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions