kasan_mempool_poison_pages(9)

bestie, welcome to the Kernel API Manual entry for kasan_mempool_poison_pages(9) — it’s giving “kernel page allocation safety check” energy and we’re gonna get into it 💖

🌸 NAME 🌸

kasan_mempool_poison_pages — check and poison a mempool page allocation. literally the whole vibe ✨

✨ SYNOPSIS ✨

bool kasan_mempool_poison_pages (struct page *page , unsigned int order
);

🎀 ARGUMENTS 🎀

• page — pointer to the page allocation, bestie 🫶
• order — order of the allocation, no cap 🌈

💅 DESCRIPTION 💅

okay so this function is made for kernel subsystems that cache page allocations so they can reuse them instead of freeing them back to page_alloc — think mempool, iykyk 👑

it’s similar to kasan_mempool_poison_object, but this one operates on page allocations instead of objects 💅

before that poisoned allocation can be reused, it must be unpoisoned via kasan_mempool_unpoison_pages — that part is not optional, bestie 😭

🦋 RETURN 🦋

it returns true if the allocation can be safely reused; otherwise it returns false ✨

🔥 SEE ALSO 🔥

• Kernel file ./include/linux/kasan.h
• kasan_unpoison_new_object(9)
• kasan_poison_new_object(9)
• kasan_slab_pre_free(9)
• kasan_slab_free(9)
• kasan_mempool_unpoison_pages(9)
• kasan_mempool_poison_object(9)
• kasan_mempool_unpoison_object(9)
• kasan_report(9)

mwah 💋 this lil page lives in source ./include/linux, dated October 2026, and it’s titled kasan_mempool_poison_pages(9) — bye bestie, go poison those pages responsibly 🫶🎀