Searched hist:"663206854 f020ec6fc6bfd3d52f501a28ede1403" (Results 1 – 3 of 3) sorted by relevance
| /linux/fs/ ! |
| H A D | mount.h | 663206854f020ec6fc6bfd3d52f501a28ede1403 Wed Jun 18 01:35:22 UTC 2025 Al Viro <viro@zeniv.linux.org.uk> copy_tree(): don't link the mounts via mnt_list
The only place that really needs to be adjusted is commit_tree() -
there we need to iterate through the copy and we might as well
use next_mnt() for that. However, in case when our tree has been
slid under something already mounted (propagation to a mountpoint
that already has something mounted on it or a 'beneath' move_mount)
we need to take care not to walk into the overmounting tree.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
| H A D | pnode.c | 663206854f020ec6fc6bfd3d52f501a28ede1403 Wed Jun 18 01:35:22 UTC 2025 Al Viro <viro@zeniv.linux.org.uk> copy_tree(): don't link the mounts via mnt_list
The only place that really needs to be adjusted is commit_tree() -
there we need to iterate through the copy and we might as well
use next_mnt() for that. However, in case when our tree has been
slid under something already mounted (propagation to a mountpoint
that already has something mounted on it or a 'beneath' move_mount)
we need to take care not to walk into the overmounting tree.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|
| H A D | namespace.c | 663206854f020ec6fc6bfd3d52f501a28ede1403 Wed Jun 18 01:35:22 UTC 2025 Al Viro <viro@zeniv.linux.org.uk> copy_tree(): don't link the mounts via mnt_list
The only place that really needs to be adjusted is commit_tree() -
there we need to iterate through the copy and we might as well
use next_mnt() for that. However, in case when our tree has been
slid under something already mounted (propagation to a mountpoint
that already has something mounted on it or a 'beneath' move_mount)
we need to take care not to walk into the overmounting tree.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
|