hlist_nulls...hed_lockless(9)

💖 hlist_nulls...hed_lockless(9) 💖

okay so we're in the Kernel API Manual, bestie, and this one is all about checking a node without taking a lock. Very main character energy, very “trust me, I checked” ✨

---

🌸 NAME 🌸

hlist_nulls_unhashed_lockless — has this node been removed and reinitialized? That's the whole question, fr fr 💅

---

🎀 SYNOPSIS 🎀

int hlist_nulls_unhashed_lockless (const struct hlist_nulls_node *h );

---

💅 ARGUMENTS 💅

• h — the node you're checking, bestie. That's it. That's the argument 🫶

---

🦋 DESCRIPTION 🦋

Quick PSA, no cap: not all removal functions leave a node in the unhashed state. Like, some do, some don't, and you gotta know which is which 😭

For example, hlist_del_init_rcu leaves the node in the unhashed state, but hlist_nulls_del does not. Not the same vibe at all 💀

Unlike hlist_nulls_unhashed, this function may be used locklessly. So if you were stressing about locks, breathe — this one's built for that lockless lifestyle 🌈

---

✨ SEE ALSO ✨

• Kernel file ./include/linux/list_nulls.h
• get_nulls_value(9)
• hlist_nulls_unhashed(9)
• hlist_nulls_for_each_entry(9)
• hlist_nulls_for_each_entry_from(9)

---

xoxo, this page is sourced from ./include/linux, dated October 2026, and the footer energy is still hlist_nulls...hed_lockless(9) 💖✨