complete_walk(9)

💅 complete_walk(9) — the Kernel API Manual, bestie edition 🦋

okay so real talk, this page lives in the complete_walk(9) section of the Kernel API Manual and it's literally the "we made it, now let's make it official" moment of a path walk. no cap, it's short but it matters. ✨

---

🌸 NAME 🌸

complete_walk — the successful-completion glow-up of a path walk 🎀

---

⭐ SYNOPSIS ⭐

int complete_walk (struct nameidata *nd );

---

🫶 ARGUMENTS 🫶

• nd — a pointer to the nameidata struct, aka the lil' state buddy carrying this whole walk around. she's the main character here 💅

---

💖 DESCRIPTION 💖

okay so picture this: if we had been chilling in RCU mode, we drop out of it and legitimize nd->path. that's it, that's the vibe shift — we're leaving the fast-and-loose era behind and making the path official. ✨

then we revalidate the final result — unless we'd already done that during the path walk, or the filesystem just doesn't ask for it. (like, respectfully, if it's already handled or nobody requested the check, we're not doing extra credit 🙈)

we return 0 on success, and -error on failure. and here's the sweet part, bestie: in case of failure, the caller does not need to drop nd->path. so don't panic-cleanup, it's handled 🫶

---

🔥 SEE ALSO 🔥

the whole friend group, ./fs/namei.c edition — literally the entire kernel file's cast list, iykyk 💀:

• 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), 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(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)

---

bestie reminder: complete_walk hands you back a legit nd->path — but on failure you do not have to drop nd->path. please don't double-free out of sheer enthusiasm 😭

---

and that's the whole page, periodt 💜 this cutie comes from ./fs and is dated October 2026 — so yeah, screenshot it, cite it, frame it, it's iconic 👑🌈