filemap_fdatawrite_range(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– filemap_fdatawrite_range β€” Kernel API Manual ✨

okay so bestie, welcome to the Kernel API Manual entry for filemap_fdatawrite_range(9) β€” the function that literally tells your dirty pages to go get written out, but only the ones chilling in a specific byte range. no cap, it's a whole thing. πŸŽ€


✨ NAME ✨

filemap_fdatawrite_range β€” start writeback on mapping dirty pages in range πŸ¦‹


🌸 SYNOPSIS 🌸

int filemap_fdatawrite_range (struct address_space *mapping , loff_t start , loff_t end );

πŸ’œ ARGUMENTS πŸ’œ

  • mapping β€” the address space structure to write, bestie. this is the thing that owns all the pages we're about to poke. πŸ‘‘
  • start β€” offset in bytes where the range starts πŸ“
  • end β€” offset in bytes where the range ends (inclusive!) β€” yes, inclusive, don't forget that part πŸ™ˆ

πŸ”₯ DESCRIPTION πŸ”₯

Start writeback against all of a mapping's dirty pages that lie within the byte offsets <start, end> inclusive. so like, the boundaries are in the club too. πŸ’…

This is a data integrity operation that waits upon dirty or in writeback pages. it's giving "i'm not leaving until everybody's sorted" energy, fr fr. 😭✨


⭐ RETURN ⭐

0 on success, negative error code otherwise. slay when it's zero, sad when it's negative. 🫢


🌈 SEE ALSO 🌈

Kernel file ./mm/filemap.c, plus literally this whole friend group:


bestie this list is LONG but every single one of them is iconic in their own way πŸ’€ don't skip a single name, they all matter.

and that's the whole page!! sign-off time: this one lives under ./mm, dated October 2026, and it's filemap_fdatawrite_range(9) β€” go forth and write back those pages, queen πŸ‘‘πŸ’–βœ¨

πŸ“¦ where this page comes from