gfs2_glock_complete(9)

📦 version 7.3.1, in nixpkgs unstable

💅 gfs2_glock_complete — the Kernel API Manual, but make it make sense

okay so bestie, welcome to the gfs2_glock_complete(9) page from the Kernel API Manual — yes that's the actual manual name, and yes we're absolutely getting into it 🫶

✨ NAME ✨

gfs2_glock_complete — the callback that the locking layer calls back into. it's giving "you rang?" energy, but for glocks 📞

🌸 SYNOPSIS 🌸

void gfs2_glock_complete (struct gfs2_glock *gl , int ret );

that's the whole signature, no cap. void in, nothing out 💀

🎀 ARGUMENTS 🎀

  • gl — a pointer to the glock. like, the glock itself. the main character 👑
  • ret — the return value from the dlm. that's it, that's the whole vibe check 🌈

🦋 DESCRIPTION 🦋

okay so here's the tea 🍓: the gl_reply field lives under the gl_lockref.lock lock, and because it's locked up all safe and cozy like that, it is totally fine to use a bitfield that's shared with other glock state fields. so you can share that bitfield, bestie — the lock has your back. no chaos, no tears, periodt ✨

lowkey the whole point: the locking is what makes the bitfield sharing okay. don't go sharing bitfields without the lock, okay? that's not the move 🙈

🔥 SEE ALSO 🔥

the whole friend group, fr fr — the Kernel file ./fs/gfs2/glock.c and everyone in it 💖:

like, that's the entire group chat and everyone ate 💅

and that's the page bestie!! 🧚 this one's filed under <pink>./fs/gfs2</pink> and dated <purple>October 2026</purple> — go read the other 40 manpages, iykyk 🎀💜

📦 where this page comes from