obj_to_location(9)

💫 obj_to_location — the kernel function that decodes your object value (manual page 9, kernel API vibes)

okay so bestie, welcome to the obj_to_location(9) glow-up 💅 this is the Kernel API Manual entry for obj_to_location, and it's literally the inverse-vibe decoder for zsmalloc land — it takes an encoded object value and hands you back where that object actually lives. no cap, it's giving "reverse the encoding and tell me the tea." 🫶

✨ NAME ✨

obj_to_location — get (<zpdesc>, <obj_idx>) from encoded object value 🌸

🎀 SYNOPSIS 🎀

void obj_to_location (unsigned long obj , struct zpdesc **zpdesc ,
       unsigned int *obj_idx );

🦋 ARGUMENTS 🦋

• obj — the encoded object value 💖 like, this is the mystery little value you're feeding in, and it's encoded, so we're about to un-encode it, periodt.
• zpdesc — zpdesc object resides in zspage ✨ (yes, that's the prose from the page verbatim-vibe — the zpdesc is the one hanging out in the zspage, iykyk).
• obj_idx — object index 🔥 the index of the object, served fresh through the pointer.

👑 SEE ALSO 👑

• Kernel file ./mm/zsmalloc.c location_to_obj(9) ⭐
• zs_lookup_class_index(9) 🌈
• zs_huge_class_size(9) 💜
• zs_malloc(9) 🍓
• zs_create_pool(9) 🧚

ngl bestie, double-check the pointer types before you go printing stuff — zpdesc and obj_idx are both out-params here (double pointer and pointer respectively), so they're where the function writes its answers 💀 the return type is void, so don't go looking for a return value, it's not coming 😭

and that's the whole page, bestie — no more options, no more flags, that's the entire tea 💅 this one shipped out of ./mm in October 2026, so go forth and decode those object values with main character energy 👑✨