iomap_fill_dirty_folios(9)

💖 iomap_fill_dirty_folios(9) 💖

okay so bestie, welcome to the Kernel API Manual — this one's a little kernel helper called iomap_fill_dirty_folios, and honestly? it's giving "tiny function, big responsibility." ✨

---

🦋 NAME 🦋

iomap_fill_dirty_folios — the way this one fills up a whole folio batch with dirty folios, no cap 💅

---

🌸 SYNOPSIS 🌸

unsigned int iomap_fill_dirty_folios (struct iomap_iter *iter , loff_t
*start , loff_t end , unsigned int *iomap_flags );

---

🎀 ARGUMENTS 🎀

• iter — the iteration structure, aka the main character of this whole operation 🫶
• start — start offset of the range. heads up bestie, this one gets updated based on how the lookup progresses, so it's not staying put 👀
• end — end offset of the range, the finish line ⭐
• iomap_flags — flags to set on the associated iomap so it can track the batch, iykyk 🏷️

---

✨ DESCRIPTION ✨

So it returns the folio count directly. like, right in the return value, not via a pointer. iconic.

It also returns the associated control flag if the batch lookup is actually performed, plus the expected offset of a subsequent lookup — both of those come out through the out params 💫

and here's the important bit, babes: the caller is responsible for setting the flag on the associated iomap. not this function. the caller. fr fr, don't forget 🙈

---

🔥 SEE ALSO 🔥

• kernel file ./fs/iomap/buffered-io.c
• iomap_read_inline_data(9)
• iomap_readahead(9)
• iomap_get_folio(9)

---

ok that's the whole page bestie, go forth and fill those dirty folios responsibly 🧚💜

mwah 💋 — this little number lives in ./fs/iomap, dated October 2026, and you just read the iomap_fill_dirty_folios(9) page. slay. periodt. 🎀