make_pbn_lock_pool(9)

✨ NAME ✨

okay so bestie, welcome to the make_pbn_lock_pool(9) page from the Kernel API Manual 💖. This function is literally here to create a new PBN lock pool and all the lock instances it can loan out ✨. That's the whole vibe: new pool, plus every lock instance it can hand out. No cap.

🎀 SYNOPSIS 🎀

int make_pbn_lock_pool (size_t capacity , struct pbn_lock_pool **pool_ptr );

💅 ARGUMENTS 💅

• capacity — the number of PBN locks to allocate for the pool. It's the lock headcount, periodt 💅.
• pool_ptr — a pointer to receive the new pool. Basically the spot where the new pool gets dropped off 🫶.

🔥 RETURN 🔥

Returns VDO_SUCCESS or an error code. That's it, that's the tea ☕✨. If it's not VDO_SUCCESS, bestie, it's an error code — no cap 😭.

🌈 SEE ALSO 🌈

if you're in your research era, these are the linked lore drops 👑:

• Kernel file ./drivers/md/dm-vdo/physical-zone.c
• vdo_is_pbn_read_lock(9)
• vdo_downgrade_pbn_write_lock(9)
• vdo_claim_pbn_lock_increment(9)
• vdo_assign_pbn_lock_provisional_reference(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)
• 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)

byeee bestie 🫶 — this page's source/version is ./drivers/md/dm-vdo, and it's dated October 2026 💜. mwah, catch you in the next man page 💋