glock_hash_walk(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

okay so this is glock_hash_walk(9), bestie β€” straight from the Kernel API Manual and here to do one iconic thing: call a function for glock in a hash bucket πŸ’…βœ¨.

πŸ¦‹ SYNOPSIS πŸ¦‹

void glock_hash_walk (glock_examiner examiner , const struct gfs2_sbd
       * sdp );

🌸 ARGUMENTS 🌸

  • examiner β€” the function. Like, literally the function being passed in 🫢.
  • sdp β€” the filesystem. That's the const struct gfs2_sbd * situation πŸ’–.

πŸ’– DESCRIPTION πŸ’–

Alright queen, here's the caveat that matters: the function can be called multiple times on the same object. So the user must ensure that the function can cope with that. No cap β€” if it can't handle repeat visits to the same object, that's the user's problem to solve πŸ™ˆπŸ’€.

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./fs/gfs2/glock.c is the hangout spot πŸ’…, and the whole squad is: wake_up_glock(9), gfs2_glock_hold(9), gfs2_glock_put(9), may_grant(9), do_error(9), find_first_holder(9), do_promote(9), find_first_waiter(9), find_last_waiter(9), state_change(9), finish_xmote(9), do_xmote(9), run_queue(9), glock_set_object(9), glock_clear_object(9), gfs2_glock_get(9), __gfs2_holder_init(9), gfs2_holder_reinit(9), gfs2_holder_uninit(9), gfs2_glock_holder_ready(9), gfs2_glock_wait(9), gfs2_glock_async_wait(9), request_demote(9), add_to_queue(9), gfs2_glock_nq(9), gfs2_glock_poll(9), gfs2_glock_dq(9), gfs2_glock_dq_uninit(9), gfs2_glock_nq_num(9), glock_compare(9), nq_m_sync(9), gfs2_glock_nq_m(9), gfs2_glock_dq_m(9), gfs2_should_freeze(9), gfs2_glock_complete(9), thaw_glock(9), gfs2_glock_thaw(9), gfs2_wait_glocks(9), dump_holder(9), gfs2_dump_glock(9) πŸ¦‹πŸŒˆ.


bestie sign-off: this page's source/version bit is ./fs/gfs2, and the date on it is October 2026 β€” it's the glock_hash_walk(9) manual. slay, go call your examiner safely πŸ’–βœ¨

πŸ“¦ where this page comes from