aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/lib/kdoc/kdoc_parser.py
diff options
context:
space:
mode:
authorAl Viro <viro@zeniv.linux.org.uk>2025-04-27 15:41:51 -0400
committerAl Viro <viro@zeniv.linux.org.uk>2025-05-09 18:02:12 -0400
commit250cf3693060a5f803c5f1ddc082bb06b16112a9 (patch)
treec884726453d713884f9b471b56f8e6d83974f482 /scripts/lib/kdoc/kdoc_parser.py
parentLinux 6.15-rc5 (diff)
downloadlinux-rng-250cf3693060a5f803c5f1ddc082bb06b16112a9.tar.xz
linux-rng-250cf3693060a5f803c5f1ddc082bb06b16112a9.zip
__legitimize_mnt(): check for MNT_SYNC_UMOUNT should be under mount_lock
... or we risk stealing final mntput from sync umount - raising mnt_count after umount(2) has verified that victim is not busy, but before it has set MNT_SYNC_UMOUNT; in that case __legitimize_mnt() doesn't see that it's safe to quietly undo mnt_count increment and leaves dropping the reference to caller, where it'll be a full-blown mntput(). Check under mount_lock is needed; leaving the current one done before taking that makes no sense - it's nowhere near common enough to bother with. Reviewed-by: Christian Brauner <brauner@kernel.org> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_parser.py')
0 files changed, 0 insertions, 0 deletions