lookup_mnt(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… lookup_mnt

okay so real talk, this one lives in the Kernel API Manual and honestly? it's a little baddie with one job and she does it flawlessly. no notes. let's get into it πŸŽ€


✨ NAME ✨

lookup_mnt β€” returns the child mount that's mounted at a given location, bestie. that's it. that's the whole vibe.


🌸 SYNOPSIS 🌸

struct vfsmount * lookup_mnt (const struct path *path );

like look at her. one argument. returns a struct vfsmount *. iconic behavior honestly πŸ¦‹


πŸŽ€ ARGUMENTS πŸŽ€

  • path β€” the location in the namespace you're curious about. the spot you're like "hmm what's mounted here" about. iykyk πŸ’…

πŸ’– DESCRIPTION πŸ’–

so here's the tea: lookup_mnt acquires and returns a new reference to the mount sitting at the location you passed in ✨

and if like... nothing is mounted there? she returns NULL. no mount, no drama, no reference. that's the whole deal 🫢

ok but for real, note the words acquires a new reference β€” that's not just flavor text, bestie, that's the actual behavior described here. don't come for me if you ignore it 😭

πŸ‘‘ SEE ALSO πŸ‘‘

all the sisters and cousins in the family, no gatekeeping πŸ’œ


🌈 and that's the page!! mwah πŸ’‹ this little cutie comes to you from ./fs and she's dated October 2026 β€” write it down, remember it, put it on your vision board ⭐ lookup_mnt(9) out. slay πŸ§šβ€β™€οΈβœ¨

πŸ“¦ where this page comes from