atomic_fetch_xor_release(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… atomic_fetch_xor_release(9) β€” the Kernel API Manual page bestie πŸ’…

okay so. this is atomic_fetch_xor_release(9), straight out of the Kernel API Manual, and honestly? she's a little icon. let's get into it 🫢


✨ NAME ✨

atomic_fetch_xor_release β€” atomic bitwise XOR with release ordering πŸ’–

πŸŽ€ SYNOPSIS πŸŽ€

int atomic_fetch_xor_release (int i , atomic_t *v );

🌸 ARGUMENTS 🌸

  • i β€” an int value. that's your xor-ingredient, bestie ✨
  • v β€” pointer to atomic_t. the main character we're actually touching πŸ’…

πŸ¦‹ DESCRIPTION πŸ¦‹

Atomically updates v to (v ^ i) with release ordering. yes, atomically β€” nobody can catch her mid-update, she moves as one unit πŸ”₯

🚨 unsafe to use in noinstr code. that's the whole vibe check you need to fail. use raw_atomic_fetch_xor_release there instead, no cap πŸ™ˆ

πŸ‘‘ RETURN πŸ‘‘

The original value of v. like, the value from before the xor happened β€” she hands you the receipt πŸ’–

⭐ SEE ALSO ⭐

lowkey the whole family showed up. the kernel file is ./include/linux/atomic/atomic-instrumented.h, and the guest list is... everyone. literally everyone 😭

and now the 64-bit girlies πŸ’œ

and the long girls, closing out the set 🧚


🌈 that's the whole page, bestie. this one comes to you from the kernel file ./include/linux/atomic β€” dated October 2026, so she's fresh πŸ’… mwah, go xor something atomically πŸŽ€

πŸ“¦ where this page comes from