gfs2_glock_nq(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’« gfs2_glock_nq β€” like, the Kernel API Manual era πŸ’«

okay bestie, so this one lives in the Kernel API Manual and it's called gfs2_glock_nq(9). it's giving "lock queue energy" and honestly? kinda iconic.


✨ NAME ✨

gfs2_glock_nq β€” enqueue a struct gfs2_holder onto a glock, which is the fancy way of saying acquire a glock. yeah. that's the whole vibe. πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

int gfs2_glock_nq (struct gfs2_holder *gh );

one function, one argument, zero drama (well, mostly β€” see RETURN below 😭).


πŸŽ€ ARGUMENTS πŸŽ€

  • gh β€” the holder structure. that's it. that's the whole argument list. she's a one-holder-argument kind of function and we respect her 🫢

🌸 DESCRIPTION 🌸

okay so the entire description is literally this:

if (gh->gh_flags & GL_ASYNC), this never returns an error

that's the whole thing. no cap. if you set the GL_ASYNC flag in gh->gh_flags, this call is never gonna hand you back an error β€” it's asynchronous, she's doing her own thing, main character energy ✨. just know that up front so you don't sit there error-checking something that's never gonna error πŸ‘‘


🌈 RETURN 🌈

she returns one of these, so keep your eyes peeled:

  • 0
  • GLR_TRYFAILED
  • or an errno on failure πŸ’€

(reminder from above: with GL_ASYNC in gh->gh_flags, it does not return an error β€” so the error branch is a non-async only kinda situation, iykyk)


πŸ’– SEE ALSO πŸ’–

this list is LONG and honestly she ate β€” the whole glock friend group showed up:

like, go read those too. or don't. but like… do 🧚


ok that's the whole page, no notes, go enqueue something πŸ”₯

and that's a wrap, bestie πŸ’œ this little gem comes to you from ./fs/gfs2, dated October 2026, and it's page gfs2_glock_nq(9) of the Kernel API Manual. slay, go touch some glocks 🌟

πŸ“¦ where this page comes from