lookup_one(9)

💅 lookup_one(9) — like, the manual page, but make it make sense

okay so this is lookup_one(9), straight out of the Kernel API Manual, section 9, bestie. it's a kernel-space function, so no, you can't just call it from your little userland script, but stick with me and you'll get it. 🫶

---

✨ SYNOPSIS ✨

struct dentry * lookup_one (struct mnt_idmap *idmap , struct qstr *name
, struct dentry *base );

that's the whole signature, no cap. it hands you back a struct dentry * — a pointer to the thing you looked up. 🎀

---

🌸 ARGUMENTS 🌸

• idmap — the idmap of the mount you're doing this lookup from. like, which mount's identity-mapping vibe are we operating under. that one. 💜
• name — a qstr holding the single pathname component you wanna look up. one component. not the whole path. iykyk. 🌈
• base — the base directory you're looking up from. your starting point, your home base, your main character directory. 👑

---

🦋 DESCRIPTION 🦋

so what does it actually do? it looks up a single pathname component. that's it, that's the whole job, and it ate. ✨

it's meant for in-kernel filesystem clients — think file servers and friends, the kind of code that lives inside the kernel and still needs to walk a path. not for you and your shell scripts, bestie, sorry. 😭

⚠️ the rule, the one you cannot skip: the caller must hold base->i_rwsem. like, actually hold it. not "hold it mentally." lock it. fr fr. 💀

---

🔥 SEE ALSO 🔥

the kernel file ./fs/namei.c is where the magic lives, and it is throwing references at us. look at this list, it's giving "linked list of destiny":

• check_acl(9)
• acl_permission_check(9)
• generic_permission(9)
• do_inode_permission(9)
• sb_permission(9)
• inode_permission(9)
• path_get(9)
• path_put(9)
• path_connected(9)
• try_to_unlazy(9)
• try_to_unlazy_next(9)
• complete_walk(9)
• may_follow_link(9)
• safe_hardlink_source(9)
• may_linkat(9)
• may_create_in_sticky(9)
• lookup_fast(9)
• start_dirop(9)
• end_dirop(9)
• kern_path_parent(9)
• vfs_path_parent_lookup(9)
• vfs_path_lookup(9)
• try_lookup_noperm(9)
• lookup_noperm(9)
• lookup_one_unlocked(9)
• lookup_one_positive_killable(9)
• lookup_one_positive_unlocked(9)
• lookup_noperm_unlocked(9)
• start_creating(9)
• start_removing(9)
• start_creating_killable(9)
• start_removing_killable(9)
• start_creating_noperm(9)
• start_removing_noperm(9)
• start_creating_dentry(9)
• start_removing_dentry(9)
• __start_renaming(9)
• start_renaming(9)
• start_renaming_dentry(9)
• start_renaming_two_dentries(9)
• vfs_prepare_mode(9)
• vfs_create(9)
• atomic_open(9)
• vfs_lookup_open(9)
• vfs_tmpfile(9)
• kernel_tmpfile_open(9)
• end_creating_path(9)
• dentry_create(9)
• vfs_mknod(9)
• vfs_mkdir(9)
• vfs_rmdir(9)
• vfs_unlink(9)
• vfs_symlink(9)
• vfs_link(9)
• vfs_rename(9)
• vfs_readlink(9)
• vfs_get_link(9)
• page_get_link(9)
• page_put_link(9)

like… go read path_get(9) and path_put(9) together, they're a matched set, it's adorable. 🫶

---

and that's the page!! you understood it, i'm so proud of you 💖 this little beauty lives in ./fs and it's dated October 2026 — so yeah, it's from the future, it's iconic, periodt. 🎀⭐👑