__gfs2_log_flush(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’« __gfs2_log_flush(9) β€” the kernel API manual, but make it make sense πŸ’«

okay bestie, so this is a page from the Kernel API Manual and the function we're hyping up today is __gfs2_log_flush β€” yes the double-underscore one, she's built different πŸ’…


✨ NAME ✨

__gfs2_log_flush β€” flush incore transaction(s) 🚽✨ (no but literally, that's what she does)


πŸ¦‹ SYNOPSIS πŸ¦‹

void __gfs2_log_flush (struct gfs2_sbd *sdp , struct gfs2_glock *gl ,
u32 flags );

like, that's the whole signature, no cap. returns void, so don't go looking for a return value bestie, she gives you nothing back and she's iconic for it 🫢


🌸 ARGUMENTS 🌸

  • sdp β€” The filesystem. yeah. the whole filesystem. main character energy fr fr πŸ‘‘
  • gl β€” The glock structure to flush. If NULL, flush the whole incore log β€” so passing NULL means she goes full send on everything 😭
  • flags β€” The log header flags: GFS2_LOG_HEAD_FLUSH_* and debug flags πŸŽ€ (yeah it's a whole family of constants plus the debug ones, noted)

πŸŽ€ SEE ALSO πŸŽ€

lowkey the friend group here is huge, so let's do a vibe check on everyone she's linked with πŸ’–

the kernel source file where she actually lives:

./fs/gfs2/log.c

and the whole crew, exactly as listed (yes all of them, I'm not skipping a single one, that's not the energy we're on ✨):

bestie note: __gfs2_log_try_reserve(9) and __gfs2_log_reserve(9) are the underscored twins of gfs2_log_try_reserve(9) and gfs2_log_reserve(9) β€” look closely, they're different entries, don't let anyone tell you otherwise πŸ™ˆ

and that's the whole page, we ate and left no crumbs πŸ“

kisses from ./fs/gfs2 β€” dated October 2026, so mark your calendar babe β­πŸ’œ

πŸ“¦ where this page comes from