d_walk(9)

📦 version 7.3.1, in nixpkgs unstable

💅 d_walk(9) — bestie's guide to walking the dentry tree 🦋

okay so this is from the Kernel API Manual, section 9, and it's literally called d_walk — yes it walks the dentry tree, the name ate and left no crumbs 💅

✨ SYNOPSIS ✨

void d_walk (struct dentry *parent , void *data , enum d_walk_ret
(*enter)(void *, struct dentry *) );

no cap, that's the whole signature — a parent dentry, your data blob, and an enter callback. that's it, that's the vibe 🎀

🌸 ARGUMENTS 🌸

  • parent — where the walk starts. the starting point, the main character, the origin story 🫶
  • data — the data that gets passed along to enter and to finish. it makes the whole journey with you, no leaving anyone behind 💖
  • enter — the callback that fires when you first enter the dentry. first impressions matter, bestie ✨

👑 DESCRIPTION 👑

ngl the description is short and iconic: the enter callbacks are called with d_lock held. 🔥

like… that's the whole thing. d_lock is held when your enter callback runs. noted, memorized, tattooed, periodt. 💀

real talk: since it's held for you, don't go doing anything cursed in there — the manpage doesn't elaborate, so i'm not gonna invent lore. just know the lock is held, iykyk.

🌈 SEE ALSO 🌈

here's the whole friend group, all from the Kernel file ./fs/dcache.c — every single one, in order, because i don't do half-finished playlists 💜

the way that's a whole squad 😭 go read enum d_walk_ret(9) first tho, it's giving prerequisites 🧚

🍓 SIGN-OFF 🍓

this lil page lives in ./fs, and it's dated October 2026 — go off, future girlies 💅✨

stay locked, stay walked, and don't forget the d_lock bestie 😌💖

📦 where this page comes from