folio_end_read(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… folio_end_read β€” the folio_end_read(9) page, bestie edition

okay so welcome to the folio_end_read(9) glow-up ✨ this one lives in the Kernel API Manual and honestly? she's short, she's sweet, she's important. let's get into it 🫢


🌸 NAME 🌸

folio_end_read β€” literally just: end read on a folio. that's the whole vibe. periodt.


✨ SYNOPSIS ✨

void folio_end_read (struct folio *folio , bool success );

like yes that's the entire signature, no cap πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • folio β€” The folio. that's her. that's the main character of this whole page 🌟
  • success β€” true if all reads completed successfully. like, did everything actually work? yes or no, no in-between πŸ™ˆ

πŸ’– DESCRIPTION πŸ’–

so here's the tea β˜• when all reads against a folio have completed, filesystems should call this function to let the pagecache know that no more reads are outstanding. it's literally the "we're done here, bestie" signal 🫑

this will unlock the folio and wake up any thread sleeping on the lock. yeah, she wakes the whole group chat up 😭

and the folio will also be marked uptodate if all reads succeeded. slay. that's the reward for a job well done βœ¨πŸ‘‘


πŸ¦‹ CONTEXT πŸ¦‹

  • may be called from interrupt or process context. both? both. flexible queen πŸ’…
  • may not be called from NMI context. nope. not there. do not do it πŸš«πŸ’€
fr fr, respect the NMI restriction. it's not a vibe check you want to fail.

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./mm/filemap.c, and the whole squad:

iykyk πŸ’œ that's the entire friend group, no one left out.


and that's the page!! πŸ’– this little gem comes to you from the ./mm source, dated October 2026 β€” go forth and end those reads, bestie 🧚🌸⭐

πŸ“¦ where this page comes from