launch_dedupe(9)

okay so bestie, this is launch_dedupe(9) from the Kernel API Manual — the little reservation desk for dedupe refcounts, and honestly it's giving “I got you” energy 💅✨

💖 NAME 💖

launch_dedupe — reserve a reference count increment for a data_vio and launch it on the dedupe path. no cap, that's the whole vibe 🦋

✨ SYNOPSIS ✨

void launch_dedupe (struct hash_lock *lock , struct data_vio *data_vio ,
       bool has_claim );

🎀 ARGUMENTS 🎀

• lock — the hash lock. that's the lock bestie, the main character of this hash-lock situation 🔥
• data_vio — the data_vio you're deduplicating using the hash lock. yes, using the hash lock, periodt 💜
• has_claim — True if the data_vio already has claimed an increment from the duplicate lock. like, it already called dibs on an increment 🙈

🌸 DESCRIPTION 🌸

So if no increments are available, this will roll over to a new hash lock and launch the data_vio as the writing agent for that lock. literally rolling over and handing it the writing-agent crown 👑 — no increments? new hash lock, writing agent, slay.

🦋 SEE ALSO 🦋

Kernel file ./drivers/md/dm-vdo/dedupe.c 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), 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), vdo_continue_hash_lock(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)

that's the whole page bestie 🫶 this one comes from the source path ./drivers/md/dm-vdo, and the date on it is October 2026 — mwah, go dedupe something cute 💖✨