vdo_allocate_block_in_zone(9)

🎀 NAME 🎀

okay bestie, meet vdo_allocate_block_in_zone(9) — yes, from the Kernel API Manual — and its whole thing is: attempt to allocate a block in the current physical zone, and if that fails try the next if possible. That's the assignment, no cap. ✨

💅 SYNOPSIS 💅

bool vdo_allocate_block_in_zone (struct data_vio *data_vio );

🫶 ARGUMENTS 🫶

• data_vio — the data_vio needing an allocation. That's the little main character here. 🎀

🔥 RETURN 🔥

Returns true if a block was allocated. If not, the data_vio will have been dispatched, so the caller must not touch it — literally hands off, bestie, do not poke it. 😭

Translation: true = slay, allocation happened. Not true = the data_vio is already out the door, so touching it is a no-no.

🌈 SEE ALSO 🌈

Kernel file ./drivers/md/dm-vdo/physical-zone.c, plus the whole friend group:

• 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)
• 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_release_physical_zone_pbn_lock(9)
• vdo_dump_physical_zone(9)

source/version: ./drivers/md/dm-vdo · date: October 2026 · page: vdo_allocate_block_in_zone(9). bye bestie, go allocate responsibly 💖🦋