iomap_iter_srcmap(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… iomap_iter_srcmap β€” from the Kernel API Manual, bestie

Okay so we're deep in the kernel API docs rn and this one is iomap_iter_srcmap(9) β€” yes the manual name is literally part of the title, we're keeping it, it's giving official ✨


🌸 NAME 🌸

iomap_iter_srcmap β€” bestie, it returns the source map for the current iomap iteration. That's the whole job. Iconic, lowkey.


πŸ¦‹ SYNOPSIS πŸ¦‹

const struct iomap * iomap_iter_srcmap (const struct iomap_iter *i );

Look at her. Const-correct on both ends. She's not gonna touch your data, she's just gonna look at it respectfully 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • i β€” the iteration structure. That's it, that's the whole argument list. Just hand her the iter struct and she'll do the rest, no cap.

πŸ’– DESCRIPTION πŸ’–

So here's the vibe: write operations on file systems with reflink support might need, like, two maps β€” a source and a destination. Not one. Two. Because reflink is extra like that πŸ’…

This function returns the source map for a given operation. And ngl, that source map may or may not be identical to the destination map sitting in i->iomap β€” so don't just assume they're the same thing, bestie, check first πŸ™ˆ

That's literally the whole function. Small, focused, does one thing. Main character energy fr fr ⭐


πŸ”₯ SEE ALSO πŸ”₯

Go read the whole iomap friend group, they're all interconnected and honestly obsessed with each other 🌈


Sign-off time 🧚 This little beauty lives over in ./include/linux, dated October 2026. Screenshot it, save it, tattoo it on your forearm β€” whatever helps you remember πŸ’œπŸ’–βœ¨

πŸ“¦ where this page comes from