__kcsan_check_read_write(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

okay so bestie, gather round β€” __kcsan_check_read_write is literally the function that checks a regular read-write access for races. that's it, that's the whole job. no cap.

this page lives in the Kernel API Manual, and it's giving "short but important" energy fr fr. πŸŽ€


✨ SYNOPSIS ✨

__kcsan_check_read_write (ptr , size );

like, that's the whole call. two args, zero drama. πŸ¦‹


🌸 ARGUMENTS 🌸

  • ptr β€” the address of access. i.e. where the thing you're touching actually lives in memory. point it at your data and let kcsan do its little vibe check. πŸ“
  • size β€” the size of access. how many bytes we're out here reading/writing. be honest about it, the checker needs to know. πŸ“
bestie pls actually pass the real size, this is the whole point of the function πŸ™ˆ

πŸ‘‘ SEE ALSO πŸ‘‘

this is the part where the manpage just goes full friend-group-tagging-everyone energy. all of these are in the kernel file ./include/linux/kcsan-checks.h, and honestly? iconic lineup. πŸ”₯

(yes it lists kcsan_check_read_write(9) and __kcsan_check_read_write(9)-adjacent stuff β€” it's a whole family, they're all slaying in their own lane πŸ’œ)


and that's the page!! short, sweet, and race-free (hopefully). 🧚

sign-off time: this lil masterpiece came from the source tree at ./include/linux, dated October 2026, and it's filed under __kcsan_check_read_write(9). mwah, bye bestie πŸ’–βœ¨

πŸ“¦ where this page comes from