kcsan_flat_atomic_begin(9)

💖 NAME 💖

okay so bestie, this is kcsan_flat_atomic_begin(9), coming at you from the Kernel API Manual — and its whole vibe is literally “begin flat atomic region.” short name, clear mission, main character energy only ✨

🌸 SYNOPSIS 🌸

void kcsan_flat_atomic_begin (void );

🎀 ARGUMENTS 🎀

• void — no arguments. not a single one, bestie, it’s giving very low-maintenance 🫶

✨ DESCRIPTION ✨

okay so here’s the tea: accesses inside the atomic region may appear to race with other accesses, but they should be considered atomic. that’s the whole plot, no extra lore 💅

🦋 SEE ALSO 🦋

Kernel file to peep: ./include/linux/kcsan-checks.h — and here’s the whole related-calls squad, in order, no cap:

• __kcsan_check_access(9)
• __kcsan_mb(9)
• __kcsan_wmb(9)
• __kcsan_rmb(9)
• __kcsan_release(9)
• kcsan_disable_current(9)
• kcsan_enable_current(9)
• kcsan_nestable_atomic_begin(9)
• kcsan_nestable_atomic_end(9)
• kcsan_flat_atomic_end(9)
• kcsan_atomic_next(9)
• kcsan_set_access_mask(9)
• kcsan_begin_scoped_access(9)
• kcsan_end_scoped_access(9)
• __kcsan_check_read(9)
• __kcsan_check_write(9)
• __kcsan_check_read_write(9)
• kcsan_check_read(9)
• kcsan_check_write(9)
• kcsan_check_read_write(9)
• ASSERT_EXCLUSIVE_WRITER(9)
• ASSERT_EXCLUSIVE_WRITER_SCOPED(9)
• ASSERT_EXCLUSIVE_ACCESS(9)
• ASSERT_EXCLUSIVE_ACCESS_SCOPED(9)
• ASSERT_EXCLUSIVE_BITS(9)

and that’s the page, bestie 🫶 source/version moment: ./include/linux, dated October 2026, for kcsan_flat_atomic_begin(9) — mwah 💋✨