do_get_kexec_buffer(9)

💖 do_get_kexec_buffer(9) 💖

okay so bestie, welcome to the Kernel API Manual ✨ this one's a little function from the device-tree side of the kernel, and honestly it's giving "small but crucial" energy 🎀

---

🌸 NAME 🌸

do_get_kexec_buffer — grab the address and size out of a device tree property 🦋

like, it literally reads a property and hands you back where it lives and how big it is. that's the whole vibe 💅

---

✨ SYNOPSIS ✨

int do_get_kexec_buffer (const void *prop , int len , unsigned long
*addr , size_t *size );

yes the signature really is formatted like that, we don't gatekeep 😌

---

🫶 ARGUMENTS 🫶

• prop — the device tree property itself 💖 the actual blob you're pulling from
• len — size of prop, so the function knows how much property it's looking at
• addr — out-param city 🏙️ it returns the address of the node through this pointer
• size — also an out-param, and it returns the size of the node here 🌸

so you pass in the property + its length, and you get back the address and size of the node. two in, two out. balanced. iconic 👑

---

⭐ RETURN ⭐

0 on success 🎉 or a negative errno on error 😭 (ngl, always check it, bestie — 0 is the only happy number here)

---

🦋 SEE ALSO 🦋

• kernel file ./drivers/of/kexec.c — that's the home base for all of this 💜
• fdt_find_and_del_mem_rsv(9)
• get_addr_size_cells(9)
• ima_get_kexec_buffer(9)
• ima_free_kexec_buffer(9)
• remove_ima_buffer(9)
• setup_ima_buffer(9)

read the whole little family, they all belong together fr fr 🌈

---

lowkey reminder: do_get_kexec_buffer only reads the property into addr and size — don't go assuming it does anything else, because it doesn't 🫶

---

and that's the page, bestie 💅✨ it lives in ./drivers/of, and this lil drop is dated October 2026 — go forth and read your device tree properties with confidence 👑🎀💖