atomic_long_...dnot_release(9)

📦 version 7.3.1, in nixpkgs unstable

💅 atomic_long_fetch_andnot_release — from the Kernel API Manual 🎀

okay so bestie, welcome to another ✨ Kernel API Manual ✨ page, and this one is a genuine little baddie. Her government name is atomic_long_fetch_andnot_release(9) (yes that's a lot of name, she ate and left no crumbs).

🌸 NAME 🌸

atomic_long_fetch_andnot_release — it does an atomic bitwise AND NOT with release ordering. Sounding very serious and very powerful, honestly iconic.

🦋 SYNOPSIS 🦋

long atomic_long_fetch_andnot_release (long i , atomic_long_t *v );

🎀 ARGUMENTS 🎀

  • i — a long value. that's it, that's the whole vibe. she's just a long.
  • v — pointer to an atomic_long_t. she's the main character here ngl, this is the thing getting updated.

✨ DESCRIPTION ✨

okay so the whole thing: it atomically updates v to (v & ~i) with release ordering. like, the math is v & ~i, the delivery is atomic, the ordering is release. she does it all and she does it without racing anybody. slay.

🚨 lowkey important warning bestie: this is unsafe to use in noinstr code. use raw_atomic_long_fetch_andnot_release there instead. do not come for me if you ignore this, fr fr, i warned you 💀

🫶 RETURN 🫶

it returns the original value of v — so like, the value from before the glow-up. you get the before picture, the variable gets the after picture. everybody wins 💖

🌈 SEE ALSO 🌈

found in the kernel file ./include/linux/atomic/atomic-instrumented.h — and bestie, she has so many cousins. like, an entire family reunion. buckle up 🎢

and that's the page bestie!! 🧚💜 this one came out of ./include/linux/atomic and it's dated October 2026 — so like, future girlie behavior honestly. stay atomic, stay ordered, and don't forget the raw_ version in noinstr code. mwah 💋🎀⭐

📦 where this page comes from