summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorChristian Brauner <brauner@kernel.org>2026-09-23 14:28:00 +0200
committerChristian Brauner <brauner@kernel.org>2026-09-25 17:20:33 +0200
commit3f5dc09141a7bfe286620a6869d1d70ffe32d6b8 (patch)
treef5fd33069d0c9f5f7c88730a4374a043e1ab93a4 /tools/perf/scripts/python/stackcollapse.py
parent7eb84d54fac5002bd975d1de8fd61d57e89172ab (diff)
downloadlinux-next-3f5dc09141a7bfe286620a6869d1d70ffe32d6b8.tar.gz
linux-next-3f5dc09141a7bfe286620a6869d1d70ffe32d6b8.zip
docs: update the unmount propagation rule
Section 5f still describes the rule propagate_umount() used before commit f0d0ba19985d ("Rewrite of propagate_umount()"). It states that a mount that receives the unmount by propagation is left alone as soon as it has any submount. That's not true anymore. A propagated unmount unmounts a mount with sub-mounts as long as every sub-mount gets unmounted together with it. This is the case when the sub-mounts are unmounted by the same propagation. Only a sub-mount that cannot be unmounted keeps its parent mounted. The section also only describes a single mount without sub-mounts. But lazy unmounts take a tree and every mount of the tree propagates its unmount from its parent mount. Link: https://patch.msgid.link/20260923-work-mount-fixes-v1-8-f424cf8d3242@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