kho_retrieve_subtree(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… kho_retrieve_subtree(9)

okay bestie, so this one is from the Kernel API Manual and it's literally the "hey, can I get that blob back" function πŸŽ€


✨ NAME ✨

kho_retrieve_subtree β€” retrieve a preserved sub blob by its name. that's it, that's the whole vibe 🫢


πŸ¦‹ SYNOPSIS πŸ¦‹

int kho_retrieve_subtree (const char *name , phys_addr_t *phys , size_t
       *size );

🌸 ARGUMENTS 🌸

  • name β€” the name of the sub blob passed to kho_add_subtree. like the little name tag on its lil backpack πŸŽ’
  • phys β€” if found, the physical address of the sub blob is stored in phys. that's the whole point, bestie πŸ’–
  • size β€” if not NULL and found, the size of the sub blob is stored in size. so it's optional and conditional, she's high-maintenance like that πŸ’…

πŸ‘‘ DESCRIPTION πŸ‘‘

Retrieve a preserved sub blob named name and store its physical address in phys and optionally its size in size.

literally that simple. you give her the name, she gives you the address, and if you pass a non-NULL size she'll drop the size in there too. no cap ✨

ngl, the size pointer is the sneaky optional one β€” not NULL and found are both required before anything gets written there. iykyk 🧚

⭐ RETURN ⭐

  • 0 on success 🌈
  • error code on failure πŸ’€

🌺 SEE ALSO 🌺

Kernel file ./kernel/liveupdate/kexec_handover.c


and that's the whole page, bestie β€” go read the whole family, they all slay together πŸ”₯

this masterclass in blob retrieval lives in ./kernel/liveupdate, dated October 2026, and she's serving kho_retrieve_subtree(9) realness πŸ’œ periodt.

πŸ“¦ where this page comes from