refcount_dec_and_test(9)

✨ refcount_dec_and_test(9) ✨

okay so this is a page from the Kernel API Manual — it's refcount_dec_and_test(9), and bestie, it's literally the "one down, is it zero?" girlie of the refcount family 💅

---

🌸 NAME 🌸

refcount_dec_and_test — decrement a refcount and test if it is 0

🎀 SYNOPSIS 🎀

bool refcount_dec_and_test (refcount_t *r );

🫶 ARGUMENTS 🫶

• r — the refcount. that's it, that's the whole argument. she's the refcount we're about to knock down a peg 🍓

💖 DESCRIPTION 💖

so, she's similar to atomic_dec_and_test, but with ✨consequences✨ — she will WARN on underflow, and she straight-up fails to decrement when the count is saturated at REFCOUNT_SATURATED. no cap, she just refuses. that's the boundary, bestie, we don't cross it 🙈

on the ordering side she's doing the absolute most (and honestly? iconic): she provides release memory ordering, so that prior loads and stores are done before — and on success she provides an acquire ordering such that free must come after. so like, the free comes last, always, no cutting the line 💀

🔥 RETURN 🔥

• true if the resulting refcount is 0
• false otherwise

👑 SEE ALSO 👑

Kernel file ./include/linux/refcount.h — plus the whole refcount friend group, go say hi 🦋

• refcount_set(9)
• refcount_set_release(9)
• refcount_read(9)
• refcount_add_not_zero(9)
• refcount_add_not_zero_acquire(9)
• refcount_add(9)
• refcount_inc_not_zero(9)
• refcount_inc_not_zero_acquire(9)
• refcount_inc(9)
• refcount_sub_and_test(9)
• refcount_dec(9)

---

ngl, if you're touching refcounts you should read the whole header. the vibes are immaculate and the saturation rules are not a joke 🌈

---

and that's the whole page, bestie ✨ shoutout to ./include/linux for hosting her and to October 2026 for the timestamp — she's dated, she's documented, she's serving main character energy, periodt 💜🎀