netfs_dirty_folio(9)

okay so bestie, this is the Kernel API Manual page for netfs_dirty_folio(9), and it's giving tiny-but-important writeback energy. 💅

---

✨ NAME ✨

netfs_dirty_folio — Mark folio dirty and pin a cache object for writeback. That's the whole assignment, no cap. 🫶

---

🌸 SYNOPSIS 🌸

bool netfs_dirty_folio (struct address_space *mapping , struct folio *folio );

---

🦋 ARGUMENTS 🦋

• mapping — the mapping the folio belongs to. Like, the folio's home base. 🏡
• folio — the folio being dirtied. Yes, we're making it dirty in the kernel sense, bestie 😭

---

💖 DESCRIPTION 💖

So the move here is: Set the dirty flag on a folio and pin an in-use cache object in memory so that writeback can later write to it. It's literally a little “hey, this one has changes” moment, plus keeping the cache object pinned so writeback can do its thing later. 🔥

This is intended to be called from the filesystem's ->dirty_folio method. That's the plug-in point, iykyk. ⭐

---

👑 RETURN 👑

true if the dirty flag was set on the folio, false otherwise. No mystery, no vibe check needed. 💀

---

🌈 SEE ALSO 🌈

Kernel file ./fs/netfs/misc.c plus these very iconic friends:

• netfs_alloc_folioq_buffer(9)
• netfs_free_folioq_buffer(9)
• netfs_unpin_writeback(9)
• netfs_clear_inode_writeback(9)
• netfs_invalidate_folio(9)
• netfs_release_folio(9)
• netfs_clear_stale_isize(9)

---

okay bye bestie 💅 — this one's signed off from ./fs/netfs, dated October 2026, and it belongs to the netfs_dirty_folio(9) manual era. 🫶💖