kasan_unpoison_new_object(9)

💖 NAME

kasan_unpoison_new_object — Temporarily unpoison a new slab object. This is the kasan_unpoison_new_object(9) page from the Kernel API Manual, and bestie, we’re getting into slab-allocator lore 💅✨

✨ SYNOPSIS ✨

Copy this exactly, no freestyling:

void kasan_unpoison_new_object (struct kmem_cache *cache , void *object
);

🫶 ARGUMENTS

• cache — the cache the object belongs to (struct kmem_cache *). It’s giving “which slab cache is this object hanging out in?” 🎀
• object — pointer to the object (void *). Literally the object pointer, no cap.

🦋 DESCRIPTION

This function is intended for the slab allocator’s internal use. It temporarily unpoisons an object from a newly allocated slab and does not do anything else. That’s the whole assignment — no extra side quests, no bonus behavior. The object must later be repoisoned by kasan_poison_new_object. Important: must, bestie. Don’t leave it unpoisoned and ghost it 😭

🌈 SEE ALSO

Kernel file: ./include/linux/kasan.h — that’s where the kernel-side lore lives.

• 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)
• kasan_report(9)

That’s the page, bestie 🫶 Source/version: ./include/linux; date: October 2026; title: kasan_unpoison_new_object(9). Stay iconic, keep your objects repoisoned, and bye 💖🎀✨