kmemleak_update_trace(9)

kmemleak_update_trace(9) 💅

okay so bestie, this is a page from the Kernel API Manual, and it is lowkey iconic. We're talking about kmemleak_update_trace, and it's giving tiny-but-mighty main character energy. ✨

🌸 NAME 🌸

kmemleak_update_trace — update object allocation stack trace 🎀

✨ SYNOPSIS ✨

void __ref kmemleak_update_trace (const void *ptr );

That signature is literally the whole vibe check — copy it exactly, iykyk. 💅

🎀 ARGUMENTS 🎀

• ptr — pointer to beginning of the object. That's it, that's the argument. 🫶

💖 DESCRIPTION 💖

Okay so here's the tea: kmemleak_update_trace() is your override bestie for the object allocation stack trace. You use it for cases where the actual allocation place is not always useful. No cap, fr fr. 🦋

The way that it just swoops in and overrides the object allocation stack trace when the actual allocation place is not always useful? Obsessed. ✨

🦋 SEE ALSO 🦋

Kernel file ./mm/kmemleak.c is right here, and these little icons are all in the same orbit:

• kmemleak_alloc(9)
• kmemleak_alloc_percpu(9)
• kmemleak_vmalloc(9)
• kmemleak_free(9)
• kmemleak_free_part(9)
• kmemleak_free_percpu(9)
• kmemleak_not_leak(9)
• kmemleak_transient_leak(9)
• kmemleak_ignore_percpu(9)
• kmemleak_ignore(9)
• kmemleak_scan_area(9)
• kmemleak_no_scan(9)
• kmemleak_alloc_phys(9)
• kmemleak_free_part_phys(9)
• kmemleak_ignore_phys(9)

mwah 💖 this page comes from ./mm, dated October 2026, and it's literally called kmemleak_update_trace(9) — periodt. 👑