gfs2_ail1_empty_one(9)

💅 gfs2_ail1_empty_one(9) 💅

okay so bestie, welcome to the Kernel API Manual ✨ — this is a kernel function page, and yes it's a (9) page, which is the section for kernel routines, iykyk 🧚

🌸 NAME 🌸

gfs2_ail1_empty_one — the vibe check for a trans in the AIL: has it been synced or not? 👀

✨ SYNOPSIS ✨

int gfs2_ail1_empty_one (struct gfs2_sbd *sdp , struct gfs2_trans *tr ,
int *max_revokes );

like literally that's the whole signature, no cap 🫶

🎀 ARGUMENTS 🎀

• sdp — the filesystem, the main character of this whole operation 👑
• tr — the transaction, the one we're checking on 🦋
• max_revokes — if this is nonzero, we go ahead and issue revokes for the bd items belonging to the written buffers. not zero? revokes get issued. periodt 💅

⭐ RETURN ⭐

the transaction's count of remaining active items 🔥 — that's your number, that's what you get back.

🌈 SEE ALSO 🌈

kernel file ./fs/gfs2/log.c 💖 and friends:

gfs2_struct2blk(9), gfs2_remove_from_ail(9), gfs2_ail1_start_one(9), gfs2_ail1_flush(9), gfs2_ail1_start(9), gfs2_ail1_empty(9), gfs2_log_is_empty(9), gfs2_log_release_revokes(9), gfs2_log_release(9), __gfs2_log_try_reserve(9), __gfs2_log_reserve(9), gfs2_log_try_reserve(9), gfs2_log_reserve(9), log_distance(9), calc_reserved(9), gfs2_flush_revokes(9), gfs2_write_log_header(9), log_write_header(9), gfs2_ail_drain(9), empty_ail1_list(9), gfs2_trans_drain(9), __gfs2_log_flush(9), gfs2_merge_trans(9), gfs2_log_commit(9), gfs2_log_shutdown(9), gfs2_logd(9)

and that's the whole page, bestie — no crumbs left 🍓 this came out of ./fs/gfs2, dated October 2026, and it's living in the Kernel API Manual forever 💜 slay 🎀