may_umount_tree(9)

🌸 NAME 🌸

okay so bestie, this is may_umount_tree — it's giving "check if a mount tree is busy" energy 💅 like literally, that's the whole job ✨

---

🦋 SYNOPSIS 🦋

int may_umount_tree (struct vfsmount *m );

that's it, that's the function, no cap 🫶

---

🎀 ARGUMENTS 🎀

• m — the root of the mount tree 🌳 like the actual top of the whole tree structure, okurrr

---

💖 DESCRIPTION 💖

so the way this works is: you call may_umount_tree to check whether a whole tree of mounts has anything busy going on in there 👀

and what counts as busy? glad you asked bestie, the vibes check is:

• any open files 📂
• pwds (yep, process working directories are holding on 😭)
• chroots
• sub mounts that are busy

if any of those are hanging around, the tree is busy, and that is literally the whole vibe check 🙈✨

---

🧚 SEE ALSO 🧚

okay this part is the friend group, and they're all in the kernel file ./fs/namespace.c — go say hi 👋💜

• mnt_get_write_access(9)
• mnt_want_write(9)
• mnt_get_write_access_file(9)
• mnt_want_write_file(9)
• mnt_put_write_access(9)
• mnt_drop_write(9)
• mnt_hold_writers(9)
• mnt_unhold_writers(9)
• __lookup_mnt(9)
• lookup_mnt(9)
• attach_mnt(9)
• vfs_create_mount(9)
• path_is_mountpoint(9)
• may_umount(9)
• clone_private_mount(9)
• attach_recursive_mnt(9)
• do_lock_mount(9)
• path_overmounted(9)
• can_move_mount_beneath(9)
• mnt_set_expiry(9)
• mnt_allow_writers(9)

---

and that's the page!! mwah 💋 before you go — this one came from the source path ./fs, dated October 2026, and it's filed under may_umount_tree(9) in the kernel API manual 📖✨ slay, go touch some mounts (safely) 🎀