folio_end_writeback(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

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

okay so real talk, this one is a tiny little function with a big responsibility, and the manpage is short enough that we can absolutely devour it in one sitting 🫢


✨ NAME ✨

folio_end_writeback β€” literally just: end writeback against a folio. that's the whole vibe. πŸ’«


πŸŽ€ SYNOPSIS πŸŽ€

void folio_end_writeback (struct folio *folio );

one function, one arg, returns nothing. no notes. πŸ‘‘


🌸 ARGUMENTS 🌸

  • folio β€” the folio. yes that's the entire description. she's mysterious, she's iconic, she contains multitudes πŸ’…

πŸ¦‹ DESCRIPTION πŸ¦‹

k so here's the one thing you cannot fumble: the folio must actually be under writeback. like, for real. it's not a "close enough" situation, it's not a "we'll figure it out" situation. it has to genuinely be in writeback rn or this is not it, bestie 😭


🧚 CONTEXT 🧚

the good news?? you can call this from process context or interrupt context. flexible queen. no cap. ✨


πŸ”₯ SEE ALSO πŸ”₯

this list is long and honestly kinda giving "she knows everybody at the party" energy, so buckle up, we're going through the whole guest list πŸ’–

all of these live in the kernel file ./mm/filemap.c:

like… 45 entries. she said "I have a support system" and she meant it πŸ’€πŸ’–


⭐ friendly reminder from your girl: that "the folio must actually be under writeback" line is the whole personality of this function. don't skip it, don't soften it, don't pretend you didn't read it πŸ™ˆ

and that's the page, bestie!! this one came from ./mm and it's dated October 2026 πŸ—“οΈβœ¨ mwah, go forth and end that writeback correctly πŸŽ€πŸ’œπŸ¦‹

πŸ“¦ where this page comes from