Searched hist:da025cdb97a23c1916d8491925b878f3e1de0bca (Results 1 – 1 of 1) sorted by relevance
| /linux/fs/ ! |
| H A D | pnode.c | da025cdb97a23c1916d8491925b878f3e1de0bca Fri Aug 15 03:32:26 UTC 2025 Al Viro <viro@zeniv.linux.org.uk> propagate_umount(): only surviving overmounts should be reparented
... as the comments in reparent() clearly say. As it is, we reparent
*all* overmounts of the mounts being taken out, including those that
are taken out themselves. It's not only a potentially massive slowdown
(on a pathological setup we might end up with O(N^2) time for N mounts
being kicked out), it can end up with incorrect ->overmount in the
surviving mounts.
Fixes: f0d0ba19985d "Rewrite of propagate_umount()"
Reviewed-by: Christian Brauner <brauner@kernel.org>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|