folio_wait_stable(9)

✨ NAME ✨

okay so welcome to the Kernel API Manual, bestie 💖 — the function is folio_wait_stable, and its whole job is: wait for writeback to finish, if necessary.

🌸 SYNOPSIS 🌸

void folio_wait_stable (struct folio *folio );

🎀 ARGUMENTS 🎀

• folio — the folio to wait on. That's it, that's the argument 🫶

🦋 DESCRIPTION 🦋

folio_wait_stable determines if the given folio is related to a backing device that requires folio contents to be held stable during writeback. If so, then it will wait for any pending writeback to complete. it's giving "hold still, we're not done yet" energy 💅

🔥 CONTEXT 🔥

• Sleeps. 😴 literally catches Zs.
• Must be called in process context and with no spinlocks held. no cap.
• Caller should hold a reference on the folio.
• If the folio is not locked, writeback may start again after writeback has finished. heads up bestie 👀

💜 SEE ALSO 💜

Kernel file ./mm/page-writeback.c — and this function's whole friend group is:

• node_dirtyable_memory(9)
• global_dirtyable_memory(9)
• domain_dirty_limits(9)
• global_dirty_limits(9)
• node_dirty_limit(9)
• node_dirty_ok(9)
• __wb_calc_thresh(9)
• balance_dirty_pages_ratelimited_flags(9)
• balance_dirty_pages_ratelimited(9)
• wb_over_bg_thresh(9)
• tag_pages_for_writeback(9)
• writeback_iter(9)
• filemap_dirty_folio(9)
• folio_redirty_for_writepage(9)
• folio_mark_dirty(9)
• folio_wait_writeback(9)
• folio_wait_writeback_killable(9)

and that's the tea 🍓 cute sign-off: source/version ./mm, date October 2026, title folio_wait_stable(9) — mwah 💋✨