is_hash_collision(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– is_hash_collision πŸ’–

okay bestie, welcome to the Kernel API Manual page for is_hash_collision(9) β€” yes, we're doing kernel hash-lock lore today and it's lowkey iconic ✨

🌸 NAME 🌸

is_hash_collision β€” check to see if a hash collision has occurred. That's the whole vibe check, no cap πŸ’…

✨ SYNOPSIS ✨

bool is_hash_collision (struct hash_lock *lock , struct data_vio
       *candidate );

πŸ’… ARGUMENTS πŸ’…

  • lock β€” the lock to check, bestie.
  • candidate β€” the data_vio seeking to share the lock; main character energy, but for lock-sharing 🫢

πŸ¦‹ DESCRIPTION πŸ¦‹

Check whether the data in data_vios sharing a lock is different than in a data_vio seeking to share the lock. This should only be possible in the extremely unlikely case of a hash collision. It's giving rare edge case, highkey why we check πŸ’€βœ¨

πŸŽ€ RETURN πŸŽ€

The return is true if the given data_vio must not share the lock because it doesn't have the same data as the lock holders. Periodt β€” that's the return value πŸŽ€

🌈 SEE ALSO 🌈


xoxo, your kernel manual bestie πŸ’– β€” source/version: ./drivers/md/dm-vdo; date: October 2026; page: is_hash_collision(9) πŸŽ€

πŸ“¦ where this page comes from