folio_putback_hugetlb(9)

💖 folio_putback_hugetlb 💖

okay so bestie, welcome to the folio_putback_hugetlb(9) page — it's a kernel API manual moment and honestly it's giving "small function, big responsibility" ✨

---

🌸 NAME 🌸

folio_putback_hugetlb — unisolate a hugetlb folio 🦋

like, it puts the folio back. that's the whole vibe. periodt.

---

✨ SYNOPSIS ✨

void folio_putback_hugetlb (struct folio *folio );

literally that's it, no return value, no drama, just vibes and a pointer 💅

---

🎀 ARGUMENTS 🎀

• folio — the isolated hugetlb folio 👑 that's the one you're putting back, the one that's currently in its isolated era

---

🔥 DESCRIPTION 🔥

okay so here's the tea ☕ — this function does the putback / un-isolate thing for a hugetlb folio that was previously isolated using folio_isolate_hugetlb. you're basically undoing the isolation arc 😭

what that actually means, fr fr:

• it marks the folio non-isolated / migratable again 🧚
• and it puts it back onto the active list 🌈

and there's a bonus detail that's lowkey important — it will drop the additional folio reference that you got through folio_isolate_hugetlb 🫶. so yeah, the reference that came with the isolation? it's leaving. it's gone. gorgeous. 💀

ngl bestie, keep track of that reference drop, because that's the part that actually matters 👀

---

🦋 SEE ALSO 🦋

• Kernel file ./mm/hugetlb.c — the whole neighborhood these functions live in 🏡
• hugetlb_alloc_folio(9)
• huge_pmd_unshare(9)
• folio_isolate_hugetlb(9) — the iconic prequel to this one, the isolation half of the story 💜

---

and that's the page!! mwah 💋 this one came from ./mm, serve date October 2026, and the whole thing is filed under folio_putback_hugetlb(9) — go put those folios back where they belong, bestie 🎀✨