vdo_continue_hash_lock(9)

💖 NAME 💖

okay so this page is literally vdo_continue_hash_lock(9) from the Kernel API Manual, and it is all about this: Continue the processing state after writing, compressing, or deduplicating. 💅✨

🌸 SYNOPSIS 🌸

void vdo_continue_hash_lock (struct vdo_completion *completion );

🎀 ARGUMENTS 🎀

• completion — The data_vio completion to continue processing in its hash lock. That is the one and only argument, bestie. 💖

🦋 DESCRIPTION 🦋

This function asynchronously continues processing a data_vio in its hash lock after it has finished writing, compressing, or deduplicating. 🎀 Why? So it can:

• share the result with any data_vios waiting in the hash lock,
• or update the UDS index,
• or simply release its share of the lock.

No cap, that is the whole vibe: async continuation in the hash lock, and those are the jobs it can do after the write/compress/dedupe situation. ✨

🧚 CONTEXT 🧚

⚠️ This must only be called in the correct thread for the hash zone. So do a vibe check on your thread first, bestie — wrong thread is not it. 😭

🌈 SEE ALSO 🌈

Kernel file ./drivers/md/dm-vdo/dedupe.c — plus the whole friend group:

• Introduction(9)
• return_hash_lock_to_pool(9)
• vdo_get_duplicate_lock(9)
• hash_lock_key(9)
• get_hash_lock_state_name(9)
• assert_hash_lock_agent(9)
• set_duplicate_lock(9)
• dequeue_lock_waiter(9)
• set_hash_lock(9)
• exit_hash_lock(9)
• set_duplicate_location(9)
• retire_lock_agent(9)
• wait_on_hash_lock(9)
• abort_waiter(9)
• start_bypassing(9)
• finish_unlocking(9)
• unlock_duplicate_pbn(9)
• start_unlocking(9)
• finish_updating(9)
• start_updating(9)
• finish_deduping(9)
• acquire_lock(9)
• enter_forked_lock(9)
• fork_hash_lock(9)
• launch_dedupe(9)
• start_deduping(9)
• increment_stat(9)
• finish_verifying(9)
• start_verifying(9)
• finish_locking(9)
• lock_duplicate_pbn(9)
• start_locking(9)
• finish_writing(9)
• select_writing_agent(9)
• start_writing(9)
• finish_querying(9)
• start_querying(9)
• report_bogus_lock_state(9)
• is_hash_collision(9)
• vdo_acquire_hash_lock(9)
• vdo_release_hash_lock(9)
• transfer_allocation_lock(9)
• vdo_share_compressed_write_lock(9)
• report_dedupe_timeouts(9)
• finish_index_operation(9)
• check_for_drain_complete(9)
• vdo_make_hash_zones(9)
• vdo_free_hash_zones(9)
• suspend_index(9)
• resume_index(9)
• vdo_resume_hash_zones(9)
• get_hash_zone_statistics(9)
• vdo_get_dedupe_statistics(9)
• vdo_select_hash_zone(9)
• dump_hash_lock(9)
• dump_hash_zone(9)
• vdo_dump_hash_zones(9)
• acquire_context(9)

okay that is the page! source/version line is ./drivers/md/dm-vdo, and the date is October 2026 — mwah 💋✨