assert_hash_lock_agent(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… assert_hash_lock_agent(9) πŸ’…

okay so welcome to the Kernel API Manual page for assert_hash_lock_agent(9), bestie. this is the little assertion helper that checks a data_vio is the agent of its hash lock, and that this is being called in the hash zone. no cap, it's giving "trust but verify" energy. ✨


🌸 NAME 🌸

assert_hash_lock_agent β€” assert that a data_vio is the agent of its hash lock, and that this is being called in the hash zone. πŸ’–

the way that this is literally a vibe check for lock-agent-ness, iykyk. 🫢


✨ SYNOPSIS ✨

here's the signature, exactly as it appears β€” don't freestyle it, bestie:

void assert_hash_lock_agent (struct data_vio *data_vio , const char
       *where );

πŸŽ€ ARGUMENTS πŸŽ€

  • data_vio β€” the data_vio that is expected to be the lock agent. this is the main character we're checking, okay? πŸ‘‘
  • where β€” a string that describes the function making the assertion. it's literally the "who is calling" receipt. 🧾

🌈 SEE ALSO 🌈

okay bestie, the SEE ALSO section is huge and we are not skipping a single one. here's the whole squad, in the original order:

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


xoxo, your kernel bestie πŸ’– β€” this page lives under ./drivers/md/dm-vdo, dated October 2026, and yes, it's literally assert_hash_lock_agent(9). periodt. 🫢

πŸ“¦ where this page comes from