__kcsan_check_write(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… __kcsan_check_write β€” check regular write access for races

okay so first things first, bestie: this lil guy lives in the Kernel API Manual, section 9, and its government name is __kcsan_check_write. Say it with me β€” it's the "hey KCSAN, I'm about to write something, pls watch for races" check πŸŽ€


✨ NAME ✨

__kcsan_check_write β€” check regular write access for races 🌸

Like, it's giving "tell the race detector that a plain ol' regular write is happening at this address, with this size." No cap, that's the whole job. πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

__kcsan_check_write (ptr , size );

yep that's it, that's the icon. two arguments, spaced all cute like the original, copy-paste it exactly and you're golden ✨


πŸ‘‘ ARGUMENTS πŸ‘‘

  • ptr β€” address of access πŸ“ like, where the write is happening, babe.
  • size β€” size of access πŸ“ how many bytes we're writing. be honest about this one fr fr.

🌈 SEE ALSO 🌈

okay this is the part where the manpage just. keeps. going. πŸ’€ but every single one of these is part of the family so we're listing them ALL, no skipping, periodt:

like, go read them, they're all lowkey iconic in their own way 🫢


ngl the whole KCSAN crew is a vibe β€” this one's just the "regular write" member of the squad, so hit up the others when you need reads, atomics, scoped access, or the ASSERT_EXCLUSIVE_* besties πŸ’œ

kay that's the whole page, mwah πŸ’‹ β€” this came straight out of ./include/linux, dated October 2026, and the header/footer literally just repeat __kcsan_check_write(9) at you because the manpage format is dramatic like that. slay. πŸ’…βœ¨

πŸ“¦ where this page comes from