iomap_read_inline_data(9)

💖 iomap_read_inline_data(9) 💖

okay so bestie, welcome to the Kernel API Manual, section 9, and today's main character is iomap_read_inline_data — she's giving tiny-but-important, and honestly? iconic. 🎀

---

✨ NAME ✨

iomap_read_inline_data — copy inline data into the page cache 💅

---

🌸 SYNOPSIS 🌸

int iomap_read_inline_data (const struct iomap_iter *iter , struct folio
*folio );

two args, one int coming back at you, no cap. 🦋

---

🧚 ARGUMENTS 🧚

• iter — the iteration structure, aka the vibe-check source of truth for what we're reading ✨
• folio — the folio to copy to, aka the destination, aka where the data goes to live its best life 🫶

---

👑 DESCRIPTION 👑

so here's the tea, bestie: this function copies the inline data sitting inside iter into folio, and then zeroes out the rest of the folio so there's no leftover ghost data lurking in there. 🙈 literal cleanup queen behavior.

Only a single IOMAP_INLINE extent is allowed at the end of each file. that's the rule, fr fr — one at the end, that's it, no stacking, no greedy little extents.

returns 0 for success — which completes the read, slay — or the usual negative errno if things did not go off. 😭

---

🔥 SEE ALSO 🔥

• Kernel file ./fs/iomap/buffered-io.c (go read her, she has lore) 📖
• iomap_readahead(9)
• iomap_get_folio(9)
• iomap_fill_dirty_folios(9)

the whole iomap friend group, honestly obsessed. 🌈

---

and that's the page!! tysm for reading, mwah 💋 — this lil angel lives in ./fs/iomap, dated October 2026, and yes she ate. ⭐💜