fork_hash_lock(9)

📦 version 7.3.1, in nixpkgs unstable

💅 fork_hash_lock(9) — Kernel API Manual ✨

okay bestie, welcome to the Kernel API Manual page for fork_hash_lock(9) — yes the whole page is literally named after the function, main character energy only 💖

🌸 NAME 🌸

fork_hash_lock — fork a hash lock because it has run out of increments on the duplicate PBN. like it hit the cap, it's done, time to split 🫶

⭐ SYNOPSIS ⭐

void fork_hash_lock (struct hash_lock *old_lock , struct data_vio
*new_agent );

that's it, that's the whole signature 💅

🎀 ARGUMENTS 🎀

  • old_lock — the hash lock you're forking. the og. the one that ran out of increments 💀
  • new_agent — the data_vio that's gonna be the agent for the brand new lock 👑

🦋 DESCRIPTION 🦋

so here's the vibe: this thing transfers the new agent and any lock waiters over to a brand new hash lock instance, and that new instance takes the place of the old lock in the lock map. slay, seamless ✨

the old lock? it doesn't get retired or anything dramatic — it remains active, but it will not update advice. that's it, that's the whole trade-off, no cap 🙈

💜 SEE ALSO 💜

like, go read these too, iykyk — kernel file ./drivers/md/dm-vdo/dedupe.c and Introduction(9), plus:

and that's the page bestie 🧚💖 this one comes to you from ./drivers/md/dm-vdo, dated October 2026 — fork_hash_lock(9), periodt ✨

📦 where this page comes from