diff options
| author | Christian Brauner <brauner@kernel.org> | 2026-10-02 15:52:41 +0200 |
|---|---|---|
| committer | Christian Brauner <brauner@kernel.org> | 2026-10-04 12:31:39 +0200 |
| commit | 921c14fd00edb1e6c1e4248a669d65e391b89b7e (patch) | |
| tree | 87b37d413ac068bb1f6c85aeb86d51a0ff5bfb4c /tools/perf/scripts/python/stackcollapse.py | |
| parent | d74d66aa708ccf2bc0b1e265a83fed0f2308d5c4 (diff) | |
| download | linux-921c14fd00edb1e6c1e4248a669d65e391b89b7e.tar.gz linux-921c14fd00edb1e6c1e4248a669d65e391b89b7e.zip | |
selftests/filesystems: check that a lock lands on the right mount and stays
Check MNT_LOCKED:
- A child in a user namespace of its own triggers the tracefs automount
through a directory descriptor on the host's debugfs mount. The copy
in the child's namespace has to be locked and the host's mount unlocked.
- A child moves a bind of that automount beneath a locked covering mount,
unmounts the covering mount and asks for the umount of an unlocked
ancestor. This must not expire the mount which holds the lock now.
- The host mounts and unmounts on a directory that a locked mount covers
in a user namespace further down the propagation chain. That cover has
to be locked afterwards as it was before.
Link: https://patch.msgid.link/20261002-work-mount-fixes-4-v1-10-dd44b89d44ce@kernel.org
Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions
