do_xmote(9)

✨ NAME ✨

okay so bestie, meet do_xmote(9) — this page is from the Kernel API Manual, and we’re folding that manual-name detail in right here near the top instead of copying the header line, because we’re iconic like that. do_xmote calls the DLM to change the state of a lock. That’s the assignment: DLM lock-state change realness, periodt.

🌸 SYNOPSIS 🌸

the function signature is giving exactly this, no edits, no vibes-based renaming:

void do_xmote (struct gfs2_glock *gl , struct gfs2_holder *gh , unsigned
int target , bool may_cancel );

🎀 ARGUMENTS 🎀

• gl — the lock state, bestie. That’s the lock whose state is getting the DLM treatment.
• gh — the holder, and heads up: only for promotes, iykyk.
• target — the target lock state. The state we’re aiming for.
• may_cancel — Operation may be canceled. Yes, cancellation is allowed here.

🦋 SEE ALSO 🦋

the Kernel file is ./fs/gfs2/glock.c, and the whole reference lineup is here — every single one, no skips:

• 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)
• 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)

🎀 final cute sign-off: source/version is ./fs/gfs2, the date is October 2026, and this page is do_xmote(9) from the Kernel API Manual. slay, go forth and xmote responsibly 💅💖