acquire_lock(9)

📦 version 7.3.1, in nixpkgs unstable

💅 acquire_lock(9) — like, the Kernel API Manual one, bestie

okay so picture this: it's giving kernel internals, it's giving dedupe energy, and the manual page literally calls itself acquire_lock(9). we're in the Kernel API Manual, babes. buckle up 🎀

✨ NAME ✨

acquire_lock — Get the lock for a record name. that's it. that's the whole vibe. 🔐

🌸 SYNOPSIS 🌸

int acquire_lock (struct hash_zone *zone , const struct uds_record_name
*hash , struct hash_lock *replace_lock , struct hash_lock **lock_ptr );

like yes she's a long signature, no we're not scared of her 💅

🦋 ARGUMENTS 🦋

  • zone — The zone responsible for the hash. she's the main character here, the one holding the vibes 👑
  • hash — The hash to lock. literally the thing we're locking, periodt.
  • replace_lock — If non-NULL, the lock already registered for the hash which should be replaced by the new lock. so like, an out-with-the-old situation 🙈
  • lock_ptr — A pointer to receive the hash lock. this is where the lock lands, hand it a spot 🫶

💖 DESCRIPTION 💖

okay so what she does: Gets the lock for the hash (record name) of the data in a data_vio, or — if one does not exist (or if we are explicitly rolling over) — initialize a new lock for the hash and register it in the zone. either way you walk out with a lock, no cap. ✨

⚠️ and this part is NOT a vibe to skip: This must only be called in the correct thread for the zone. wrong thread? no. don't. i'm serious 😭

⭐ RETURN ⭐

VDO_SUCCESS or an error code. that's the whole tea 🍓

🌈 SEE ALSO 🌈

the whole group chat, fr fr — every single one of them:

and that's the page!! 🌟 this lil icon came to you from ./drivers/md/dm-vdo, dated October 2026, under the handle acquire_lock(9). mwah, go lock something 💋🦋

📦 where this page comes from