hlist_unhashed(9)

📦 version 7.3.1, in nixpkgs unstable

💅 hlist_unhashed(9) — a Kernel API Manual moment

okay so bestie, welcome to the glow-up of hlist_unhashed, coming at you straight from the kernel API manual. pull up a chair, grab a matcha 🍵, we're doing pointer lore today.

✨ NAME ✨

hlist_unhashed — literally answering the question "has this node been removed from the list and reinitialized?" 🦋

🌸 SYNOPSIS 🌸

int hlist_unhashed (const struct hlist_node *h );

🎀 ARGUMENTS 🎀

  • h — the node we're checking, bestie. that's it. that's the whole argument. she's lowkey simple like that 💅

🔥 DESCRIPTION 🔥

so here's the tea ☕ — and this is the part where you gotta pay attention because it's giving "plot twist":

not all removal functions leave a node in the unhashed state. periodt. that's not a vibe check that goes one way for everybody.

like, for example:

  • hlist_nulls_del_init_rcu does leave the node in unhashed state 👑 slay for her
  • but hlist_nulls_del does not 🙈 nope, not her, different behavior entirely

so yeah, don't go assuming every _del variant is out here doing the same thing, because they are not. the way that these two functions live completely different lives 😭

💜 SEE ALSO 💜

okay this is the whole group chat right here, everyone showed up to the party 🫶 and yeah, they're all listed with their full (9) section energy:

and that's the whole page, bestie ✨ no cap, that was everything, not a single flag dropped 💖

fr fr go read the source before you ship it though — iykyk 🌈

later, legend 🦋 — this one's from ./scripts/include, dated October 2026, and yes she ate 👑💅

📦 where this page comes from