raw_atomic_long_fetch_or(9)

📦 version 7.3.1, in nixpkgs unstable

✨ raw_atomic_long_fetch_or ✨

okay so bestie, we're deep in the Kernel API Manual today — this is raw_atomic_long_fetch_or(9) and honestly? she's iconic. atomic bitwise OR with full ordering, no cap. 💅

🌸 NAME 🌸

raw_atomic_long_fetch_or — atomic bitwise OR with full ordering 🫶

🎀 SYNOPSIS 🎀

long raw_atomic_long_fetch_or (long i , atomic_long_t *v );

🌈 ARGUMENTS 🌈

  • i — a long value. just a long. that's her whole job. 💜
  • v — pointer to atomic_long_t. yes queen, hand over the pointer. 👑

💖 DESCRIPTION 💖

So what she does is: atomically updates v to (v | i) — with full ordering, meaning the vibes are completely in order, nothing out of sequence, periodt. 🔥

She's safe to use in noinstr code, which is lowkey a flex. but — and listen — prefer atomic_long_fetch_or elsewhere. like, outside of noinstr? use the other one. she's the special-occasion friend. 💀

⭐ RETURN ⭐

The original value of v. not the new one. the one from before. main character backstory energy. 👑

🦋 SEE ALSO 🦋

Kernel file ./include/linux/atomic/atomic-long.h

and the whole entire friend group, fr fr:

and that's the whole page, bestie!! 💖✨🎀🦋🌸💅🫶

this little love letter lives in ./include/linux/atomic, dated October 2026 — so like, mark your calendar and stan responsibly. 👑🙈🍓🧚💜

📦 where this page comes from