lookup_noperm(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… lookup_noperm(9) β€” yes bestie, we're reading a kernel API manual page today

okay so real talk, this one lives in the Kernel API Manual (section 9, the "kernel internals" girlies) and it's about looking up exactly one pathname component without doing any permission checks. it's giving "trust me bro, the caller already checked." let's get into it ✨


🌸 NAME 🌸

lookup_noperm β€” the filesystem helper that looks up a single pathname component πŸŽ€

πŸ¦‹ SYNOPSIS πŸ¦‹

struct dentry * lookup_noperm (struct qstr *name , struct dentry *base );

✨ ARGUMENTS ✨

  • name β€” a qstr holding the pathname component you wanna look up πŸ’–
  • base β€” the base directory you're looking up from 🌸

πŸ‘‘ DESCRIPTION πŸ‘‘

okay so first thing, and I need you to hear me on this one: this routine is purely a helper for filesystem usage and it should not be called by generic code. like, it's not for everyone, it's not a public vibe, it's fs-internal only πŸ™ˆ

and the headline: it does no permission checking. none. zero. not a single check. it's literally in the name, bestie πŸ’€

🚨 Also the caller MUST hold base->i_rwsem. No ifs, no buts, no "well I thoughtβ€”". You hold it. That's the whole deal. 🚨

🫢 SEE ALSO 🫢

Kernel file ./fs/namei.c, plus the entire extended universe of friends, because this page's SEE ALSO is lowkey a group chat with 58 members and we are NOT leaving anybody out πŸ‘‘


that's the whole page, periodt πŸ’œ this icon dropped from ./fs in October 2026 and honestly? she ate. go hold that i_rwsem and slay 🧚✨

πŸ“¦ where this page comes from