MEMFD_LUO_FOLIO_DIRTY(9)

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

okay so bestie, welcome to the MEMFD_LUO_FOLIO_DIRTY(9) page ✨ this is the kernel API manual for one (1) very specific flag, and honestly? she's iconic in her simplicity. let's get into it 🫶

---

✨ NAME ✨

MEMFD_LUO_FOLIO_DIRTY — literally just: the folio is dirty. that's the whole vibe. 💅

---

🌸 SYNOPSIS 🌸

MEMFD_LUO_FOLIO_DIRTY

no args, no params, no drama — it's a flag, she just exists 😌

---

🦋 DESCRIPTION 🦋

okay so here's the tea ☕ this flag is basically telling you "yep, this folio contains data from user" 💖 like it's got actual user-written content in there, she's lived a life, she's seen things.

and a non-dirty folio? that's the opposite energy entirely — it's one that was allocated (say, using fallocate(2)) but not written to. so it's like an empty notebook you bought and never touched 😭 allocated, sure, but no data, no story, no nothing. the way that a non-dirty folio is just sitting there with zero user data in it? relatable tbh 💀

so quick recap bestie: dirty = has user data, not dirty = allocated but never written to 🎀 no cap, that's the entire distinction.

---

🔥 SEE ALSO 🔥

go check these out, they're all in the same friend group fr fr 👑

• Kernel file ./include/linux/kho/abi/memfd.h — memfd Live Update ABI(9)
• MEMFD_LUO_FOLIO_UPTODATE(9) — her sister flag, also slaying
• struct memfd_luo_folio_ser(9) — the struct bestie
• struct memfd_luo_ser(9) — the other struct bestie

---

and that's the page!! 💖 ngl this one was short and sweet, which is honestly a mood. this came to you from ./include/linux/kho/abi (the source, our home base 🏠) and it's dated October 2026 ⭐ so yeah, mark your calendars, the kernel girlies were thriving that month 🌈

k bye, ily, go read your folio flags 🫶💜