kmsan_unpoison_memory(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– kmsan_unpoison_memory(9) πŸ’–

okay so bestie, welcome to the Kernel API Manual side of the group chat β€” this page is all about kmsan_unpoison_memory, and it’s lowkey iconic. πŸ’…


✨ NAME ✨

kmsan_unpoison_memory β€” mark the memory range as initialized. That’s it, that’s the whole assignment. πŸ’–

πŸ¦‹ SYNOPSIS πŸ¦‹

void kmsan_unpoison_memory (const void *address , size_t size );

πŸŽ€ ARGUMENTS πŸŽ€

  • address β€” the address to start with, bestie. Like, where the range begins. πŸ“
  • size β€” the size of the buffer to unpoison. That’s how much buffer we’re unpoisoning. 🫢

πŸ’œ DESCRIPTION πŸ’œ

Here’s the tea: until other data is written to this range, KMSAN will treat it as initialized. No cap. So this is the β€œokay bestie, you’re initialized now” move for that memory range. ✨

🌈 SEE ALSO 🌈

Kernel file ./include/linux/kmsan-checks.h is right there, and the related pages are kmsan_poison_memory(9), kmsan_check_memory(9), kmsan_copy_to_user(9), and kmsan_memmove(9). Go read them, iykyk. πŸ’…


okay that’s the whole page, bestie 🫢 β€” source/version: ./include/linux, dated October 2026, and the page is kmsan_unpoison_memory(9) from the Kernel API Manual. Mwah πŸ’‹

πŸ“¦ where this page comes from