stack_depot_save(9)

💾 stack_depot_save(9) — like, the Kernel API Manual but make it make sense

okay bestie, gather round 🫶 this one's from the Kernel API Manual and it's genuinely so useful — it's the function that shoves a stack trace into the stack depot so you can look it up later. iykyk 💅

---

✨ NAME ✨

stack_depot_save — save a stack trace to stack depot 🎀

---

🌸 SYNOPSIS 🌸

depot_stack_handle_t stack_depot_save (unsigned long *entries , unsigned
int nr_entries , gfp_t alloc_flags );

---

🦋 ARGUMENTS 🦋

• entries — pointer to the stack trace, bestie. that's the actual stack you're handing over 💖
• nr_entries — how many frames are in that stack. count 'em, don't guess 🔥
• alloc_flags — the allocation GFP flags. the vibe of the allocation, basically ✨

---

💜 DESCRIPTION 💜

so here's the thing that lowkey matters: this does not increment the refcount on the saved stack trace. not even a little. 🫠 for the full deets, go look at stack_depot_save_flags — it's giving main character energy and explains everything.

---

🌈 CONTEXT 🌈

this is one of those "only in the right context" situations, no cap. you can call it in contexts where allocations via alloc_pages are allowed ✨ — again, stack_depot_save_flags has the full story if you need more 💅

---

👑 RETURN 👑

you get back the handle of the stack trace stored in the depot 🎀 — and 0 on failure 😭 (yes, check it, bestie).

---

🌟 SEE ALSO 🌟

kernel file ./include/linux/stackdepot.h, plus the whole stack depot friend group 💖:

• stack_depot_save_flags(9)
• __stack_depot_get_stack_record(9)
• stack_depot_fetch(9)
• stack_depot_print(9)
• stack_depot_snprint(9)
• stack_depot_put(9)
• stack_depot_set_extra_bits(9)
• stack_depot_get_extra_bits(9)

---

ngl, 0 on failure is so real of it. check your return value, bestie, always. 💀

---

and that's the whole page, periodt 💅 this came out of ./include/linux, dated October 2026, and yes it's literally titled stack_depot_save(9) — slay, go save some stacks 🧚‍♀️💜