iomap_iter_srcmap(9)
π 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 π₯
- Kernel file
./include/linux/iomap.hβstruct iomap_iter(9),iomap_length_trim(9),iomap_length(9),iomap_iter_advance_full(9),iomap_iter_next(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms