rhashtable_walk_enter(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

okay so bestie, welcome to the Kernel API Manual page for rhashtable_walk_enter β€” literally the β€œInitialise an iterator” girlie πŸ’…βœ¨

✨ SYNOPSIS ✨

void rhashtable_walk_enter (struct rhashtable *ht , struct
       rhashtable_iter *iter );

🫢 ARGUMENTS 🫢

  • ht β€” the table you're walking over, bestie 🌸
  • iter β€” your hash table iterator πŸŽ€

πŸ’– DESCRIPTION πŸ’–

This function prepares a hash table walk. It's giving setup era, no cap ✨

⚠️ Note that if you restart a walk after rhashtable_walk_stop you may see the same object twice. Also, you may miss objects if there are removals in between rhashtable_walk_stop and the next call to rhashtable_walk_start. So yeah, the vibe check can get a little wobbly there 😭

For a completely stable walk you should construct your own data structure outside the hash table. That's the move for perfect stability, fr fr πŸ¦‹

This function may be called from any process context, including non-preemptible context β€” but cannot be called from softirq or hardirq context. Nope, not happening, periodt πŸ’€

You must call rhashtable_walk_exit after this function returns. Like, mandatory bestie behavior 🫢

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./lib/rhashtable.c and these iconic friends:


and that's the page, bestie πŸ’– source/version: ./lib, date: October 2026, manual page: rhashtable_walk_enter(9) β€” slay, bye βœ¨πŸŽ€

πŸ“¦ where this page comes from