diff options
| author | Al Viro <viro@zeniv.linux.org.uk> | 2025-06-22 18:03:29 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2025-07-06 11:04:14 +0200 |
| commit | 15633fe1f06d0e6a95502d6f07cf391a07a820a5 (patch) | |
| tree | da113014c4d71b3918f2bc281dd302373cbf4271 /tools/perf/scripts/python/sched-migration.py | |
| parent | 11e740dc1a2c8590eb7074b5c4ab921bb6224c36 (diff) | |
attach_recursive_mnt(): do not lock the covering tree when sliding something under it
[ Upstream commit ce7df19686530920f2f6b636e71ce5eb1d9303ef ]
If we are propagating across the userns boundary, we need to lock the
mounts added there. However, in case when something has already
been mounted there and we end up sliding a new tree under that,
the stuff that had been there before should not get locked.
IOW, lock_mnt_tree() should be called before we reparent the
preexisting tree on top of what we are adding.
Fixes: 3bd045cc9c4b ("separate copying and locking mount tree on cross-userns copies")
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/sched-migration.py')
0 files changed, 0 insertions, 0 deletions