kcsan_atomic_next(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… kcsan_atomic_next(9) β€” a Kernel API Manual moment

okay so welcome to the Kernel API Manual, bestie β€” today's episode is kcsan_atomic_next(9) and it's honestly such a little function with such a big "trust me bro, these next few accesses are atomic" energy ✨


🌸 NAME

kcsan_atomic_next β€” consider following accesses as atomic πŸŽ€


πŸ¦‹ SYNOPSIS

void kcsan_atomic_next (int n );

πŸ’œ ARGUMENTS

  • n β€” the number of following memory accesses to treat as atomic. that's it, that's the whole parameter, no cap 🫢

πŸ”₯ DESCRIPTION

Force treating the next n memory accesses for the current context as atomic operations. literally just that β€” you point at how many accesses are coming and KCSAN goes "say less, they're atomic now" πŸ’…βœ¨

ngl this is a force, so it's doing exactly what you told it to. it's not vibing, it's obeying 😭

πŸ‘‘ SEE ALSO

Kernel file ./include/linux/kcsan-checks.h β€” the main character file, go read it fr fr πŸ’–

like, the whole friend group showed up for this one πŸŒˆπŸ’œ


mwah πŸ’‹ that's the page! sign-off time: this lil legend lives in ./include/linux, it's dated October 2026, and it answers to the name kcsan_atomic_next(9) β€” slay, periodt, go treat those accesses as atomic πŸŽ€πŸ¦‹πŸ’–

πŸ“¦ where this page comes from