kmsan_slab_alloc(9)

🌸 NAME 🌸

okay so bestie, this page is from the Kernel API Manual, and the manual page is kmsan_slab_alloc(9). The function is kmsan_slab_alloc — Notify KMSAN about a slab allocation. ✨

✨ SYNOPSIS ✨

void kmsan_slab_alloc (struct kmem_cache *s , void *object , gfp_t flags
);

🎀 ARGUMENTS 🎀

• s — the slab cache that the object belongs to. That's its whole home, iykyk. 🏠
• object — the object pointer. Literally the pointer to the object, main character energy. 💅
• flags — the GFP flags passed to the allocator. Slay. 🦋

💅 DESCRIPTION 💅

Depending on the cache flags and the GFP flags, KMSAN sets up the metadata of the newly created object, marking it as initialized or uninitialized. That's the whole plot, no cap. ✨

🦋 SEE ALSO 🦋

The kernel file is ./include/linux/kmsan.h, and these are the linked besties:

• kmsan_task_create(9)
• kmsan_task_exit(9)
• kmsan_init_shadow(9)
• kmsan_init_runtime(9)
• kmsan_memblock_free_pages(9)
• kmsan_alloc_page(9)
• kmsan_free_page(9)
• kmsan_copy_page_meta(9)
• kmsan_slab_free(9)
• kmsan_kmalloc_large(9)
• kmsan_kfree_large(9)
• kmsan_ioremap_page_range(9)
• kmsan_iounmap_page_range(9)
• kmsan_handle_dma(9)
• kmsan_handle_dma_sg(9)
• kmsan_handle_urb(9)
• kmsan_unpoison_entry_regs(9)
• kmsan_get_metadata(9)
• kmsan_enable_current(9)
• kmsan_disable_current(9)
• memset_no_sanitize_memory(9)

Sign-off time, bestie 🫶 The source/version spot says ./include/linux, the date is October 2026, and the footer name is kmsan_slab_alloc(9). Mwah 💋 byeee 🎀