fiemap_prep(9)
β¨ NAME β¨
fiemap_prep(9) from the Kernel API Manual β okay bestie, this one is all about checking the validity of requested flags for fiemap. It's giving flag-bouncer-at-the-club energy π
.
π SYNOPSIS π
int fiemap_prep (struct inode *inode , struct fiemap_extent_info
*fieinfo , u64 start , u64 *len , u32 supported_flags );
πΈ ARGUMENTS πΈ
inodeβ the inode to operate on π«Ά.fieinfoβ the fiemap context passed into->fiemapβ¨.startβ start of the mapped range π.lenβ length of the mapped range, and yes, it can be truncated by this function π.supported_flagsβ the set of fiemap flags that the file system understands π.
π₯ DESCRIPTION π₯
Okay so this function must be called from each ->fiemap instance to validate the fiemap request against the file system parameters. Mandatory behavior, no cap π.
It returns 0 on success, or a negative error on failure. That's the whole vibe πβ¨.
π¦ SEE ALSO π¦
- Kernel file
./fs/ioctl.cβ plusvfs_ioctl(9),fiemap_fill_next_extent(9), andcompat_ptr_ioctl(9)π.
mwah π β this iconic page is sourced from ./fs, dated October 2026, and it's literally titled fiemap_prep(9). periodt π§π
π¦ 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