ip_vs_rht_w...ets_safe_rcu(9)

✨ ip_vs_rht_walk_buckets_safe_rcu ✨

okay bestie, so this one is a lil' function from the Kernel API Manual and honestly? it's giving "walk the buckets but make it RCU-safe" energy 💅 let's get into it.

---

🌸 NAME 🌸

ip_vs_rht_walk_buckets_safe_rcu — walk all the buckets while holding the RCU read lock 🫶

---

🎀 SYNOPSIS 🎀

ip_vs_rht_walk_buckets_safe_rcu (table , head );

---

🦋 ARGUMENTS 🦋

• table — it's a struct ip_vs_rht __rcu *table, yep the whole table, RCU-flavoured and everything ✨
• head — bucket address, used as a cursor, and its type is struct hlist_bl_head *var — that's your lil' pointer to point at where you're at 👑

---

💖 DESCRIPTION 💖

So like, you can totally use this while other people are out here adding and deleting entries — but moving is disabled. no cap, that's the deal 🙈

Using cond_resched_rcu should be safe if the tables do not change. like, if. read that again bestie 😭

fr fr, the "tables don't change" part is doing a lot of heavy lifting in that sentence — don't sleep on it 💀

---

🌈 SEE ALSO 🌈

• Kernel file ./include/net/ip_vs.h
• ip_vs_rht_for_each_table(9)
• ip_vs_rht_for_each_table_rcu(9)
• ip_vs_rht_for_each_bucket(9)
• ip_vs_rht_for_bucket_retry(9)
• DECLARE_IP_VS_RHT_WALK_BUCKETS_RCU(9)
• ip_vs_rht_walk_buckets_rcu(9)
• DECLARE_IP_VS_RHT_WALK_BUCKET_RCU(9)
• ip_vs_rht_walk_bucket_rcu(9)
• DECLARE_IP_VS_RHT_WALK_BUCKETS_SAFE_RCU(9)
• DECLARE_IP_VS_RHT_WALK_BUCKETS(9)
• ip_vs_rht_walk_buckets(9)

like, that's the whole friend group right there, go say hi 👋

---

and that's a wrap, bestie 🎀 this lil' page lives in ./include/net, dated October 2026, and it's part of the Kernel API Manual — iconic, no notes 💜