rhashtable_walk_enter(9)
π 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 afterrhashtable_walk_stopyou may see the same object twice. Also, you may miss objects if there are removals in betweenrhashtable_walk_stopand the next call torhashtable_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:
rhashtable_shrink(9)rhashtable_next_key(9)rhashtable_walk_exit(9)rhashtable_walk_start_check(9)__rhashtable_walk_find_next(9)rhashtable_walk_next(9)rhashtable_walk_peek(9)rhashtable_walk_stop(9)rhashtable_free_and_destroy(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms