mem_dump_obj(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– mem_dump_obj(9) β€” Kernel API Manual πŸ’–

okay bestie, welcome to the Kernel API Manual page for mem_dump_obj. It's giving β€œprint the receipts on this object,” and I'm obsessed. 🫢

✨ NAME ✨

mem_dump_obj β€” Print available provenance information. that's it, that's the name, periodt. πŸ’…

πŸ¦‹ SYNOPSIS πŸ¦‹

void mem_dump_obj (void *object );

🌸 ARGUMENTS 🌸

  • object β€” object for which to find provenance information. literally the object we're getting the provenance tea on. πŸ“

πŸŽ€ DESCRIPTION πŸŽ€

okay so this function uses pr_cont, so that the caller is expected to have printed out whatever preamble is appropriate. no cap β€” the preamble is the caller's job. πŸ’…

The provenance information depends on the type of object and on how much debugging is enabled. For example, for a slab-cache object, the slab name is printed, and, if available, the return address and stack trace from the allocation and last free path of that object. iconic forensic behavior, honestly. πŸ”₯

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./mm/util.c β€” and the whole SEE ALSO entourage:


byeee bestie πŸ’… this page's source/version is ./mm, dated October 2026. mwah 🫢

πŸ“¦ where this page comes from