finish_xmote(9)

okay so you opened finish_xmote(9) from the Kernel API Manual, and iykyk this is the function for when the DLM has replied to one of our lock requests 💅✨

💖 NAME

finish_xmote — The DLM has replied to one of our lock requests. That’s the whole vibe: our lock request got a reply from the DLM, and this function is the main character handling that moment 👑🔥

✨ SYNOPSIS

void finish_xmote (struct gfs2_glock *gl , unsigned int ret );

🎀 ARGUMENTS

• gl — The glock 🫶
• ret — The status from the DLM.

🌈 SEE ALSO

• Kernel file ./fs/gfs2/glock.c: 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), 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 💋 this page is signed off from ./fs/gfs2, dated October 2026, and it’s literally finish_xmote(9) — periodt 🎀🦋