vdo_assign_...al_reference(9)

💅 NAME 💅

Okay so bestie, welcome to the Kernel API Manual page for vdo_assign_...al_reference(9) — yes that's the abbreviated title, the full name is right here and it's a mouthful, no cap:

vdo_assign_pbn_lock_provisional_reference — it literally informs a PBN lock that it is the one responsible for a provisional reference. That's the whole job. It's giving "hey girl, this is yours now" energy 🫶

---

✨ SYNOPSIS ✨

void vdo_assign_pbn_lock_provisional_reference (struct pbn_lock *lock );

Returns nothing, because it's void — it just does the thing and leaves. Iconic behaviour honestly 💅

---

🎀 ARGUMENTS 🎀

• lock — the PBN lock. That's it, that's the whole argument list. She's low maintenance 🌸

---

🦋 SEE ALSO 🦋

The kernel file this lives in is ./drivers/md/dm-vdo/physical-zone.c — go read it if you're feeling brave, bestie 📖

And here's the whole friend group, everybody in the physical-zone.c clique:

• vdo_is_pbn_read_lock(9)
• vdo_downgrade_pbn_write_lock(9)
• vdo_claim_pbn_lock_increment(9)
• vdo_unassign_pbn_lock_provisional_reference(9)
• release_pbn_lock_provisional_reference(9)
• union idle_pbn_lock(9)
• struct pbn_lock_pool(9)
• return_pbn_lock_to_pool(9)
• make_pbn_lock_pool(9)
• free_pbn_lock_pool(9)
• borrow_pbn_lock_from_pool(9)
• initialize_zone(9)
• vdo_make_physical_zones(9)
• vdo_free_physical_zones(9)
• vdo_get_physical_zone_pbn_lock(9)
• vdo_attempt_physical_zone_pbn_lock(9)
• allocate_and_lock_block(9)
• retry_allocation(9)
• continue_allocating(9)
• vdo_allocate_block_in_zone(9)
• vdo_release_physical_zone_pbn_lock(9)
• vdo_dump_physical_zone(9)

---

💖 That's the whole page, bestie — short, sweet, and 100% facts. Now go assign that provisional reference, you absolute main character 👑

---

Sign-off szn 🎀: this little masterpiece comes from ./drivers/md/dm-vdo, dated October 2026, and the page itself is vdo_assign_...al_reference(9). Mwah 💋