kasan_report(9)

💅 kasan_report (9) — Kernel API Manual

okay so bestie, welcome to the kasan_report page 💖 this is a kernel API manual moment, and no, it's not that kind of report — it's the "girl, your memory access was BAD" kind of report 🔥

---

✨ NAME ✨

kasan_report — print a report about a bad memory access detected by KASAN 🫶

like, KASAN caught something sus and this is the function that spills all the tea about it 💅

---

🎀 SYNOPSIS 🎀

bool kasan_report(const void *addr, size_t size, bool is_write, unsigned long ip);

it's giving "four arguments, one bool coming back at you" ✨

---

🌸 ARGUMENTS 🌸

• addr — the address of the bad access 📍 literally the exact spot where things went wrong, iconic of it to show up
• size — the size of the bad access 📏 how much memory was involved in this whole situation
• is_write — whether the bad access is a write or a read ✍️ it's a yes/no vibe check: true = write, false = read, no in-between bestie
• ip — the instruction pointer for the accessibility check or the bad access itself 🧭 so like, either where the check happened or where the bad access itself happened, iykyk

ngl every single one of these gets passed straight into the report, so get them right or the tea will be wrong 🙈

---

👑 SEE ALSO 👑

the kernel file ./include/linux/kasan.h is right there being the main character, and it's also serving these icons 🦋

• kasan_unpoison_new_object(9)
• kasan_poison_new_object(9)
• kasan_slab_pre_free(9)
• kasan_slab_free(9)
• kasan_mempool_poison_pages(9)
• kasan_mempool_unpoison_pages(9)
• kasan_mempool_poison_object(9)
• kasan_mempool_unpoison_object(9)

---

and that's the whole page, bestie, you ate that 💅 this one lives in ./include/linux and it's dated October 2026 — take that info and slay ✨🎀💖