slab_folio(9)

💅 slab_folio(9) — the kernel API manual, but make it make sense 🎀

okay bestie, welcome to slab_folio(9), straight out of the Kernel API Manual ✨ this one is short, it's sweet, and it's lowkey a "please don't do it yourself" PSA. let's get into it 🫶

---

🌸 NAME 🌸

slab_folio — the folio that got allocated for a slab. that's it, that's the whole vibe 💖

---

✨ SYNOPSIS ✨

slab_folio (s );

one argument, no drama, we love to see it 👑

---

🎀 ARGUMENTS 🎀

• s — the slab. the actual slab in question, the main character of this function call 🌟

---

🦋 DESCRIPTION 🦋

okay so here's the lore. slabs are allocated as folios — those bigger chunks that hold all the individual objects inside them — and they're using some fields in the first struct page of the folio. and like, those fields are now accessed by struct slab instead. plot twist, i know 😭

so sometimes, occasionally, you gotta convert back to a folio, because you need to communicate with the rest of the mm. think of it as switching back to the group-chat language so everyone else can understand you 💬

please use this helper function instead of casting yourself, okay? 🥺 like genuinely. the implementation may change in the future, and if you hardcoded a cast you're gonna be the one crying about it. this helper is the whole reason we can't have nice things — no wait, it is the nice thing. use it. periodt 💅

ngl, this is the "trust the abstraction, babe" moment of the mm subsystem 🌈

---

⭐ SEE ALSO ⭐

• kernel file ./mm/slab.h
• page_slab(9)
• slab_page(9)

go read those too, iykyk 👀

---

and that's the whole page, bestie!! 🎉 courtesy of the Kernel API Manual, sourced from ./mm, dated October 2026 — genuinely iconic energy, no cap 💜🧚✨