do_error(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… do_error(9) πŸ’…

okay bestie, welcome to the Kernel API Manual β€” manual name folded in right here because we are cute and efficient like that. This page is short, but it still ate. πŸ’–


✨ NAME ✨

do_error β€” when Something unexpected has happened during a lock request. not me being dramatic, that’s literally the plot 😭


πŸŽ€ SYNOPSIS πŸŽ€

copy this exactly, bestie β€” no autocorrect, no vibes-based edits:

void do_error (struct gfs2_glock *gl , const int ret );

🌸 ARGUMENTS 🌸

  • gl β€” the glock πŸ‘‘
  • ret β€” the status from the DLM πŸ’…

that’s the whole cast, and they understood the assignment.


πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file: ./fs/gfs2/glock.c β€” and the group chat is huge, so every single handle is here: wake_up_glock(9), gfs2_glock_hold(9), gfs2_glock_put(9), may_grant(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), glock_hash_walk(9), thaw_glock(9), gfs2_glock_thaw(9), gfs2_wait_glocks(9), dump_holder(9), gfs2_dump_glock(9) πŸ’–


mwah πŸ’– β€” source/version ./fs/gfs2, date October 2026, page do_error(9). periodt.

πŸ“¦ where this page comes from