continue_allocating(9)

✨ continue_allocating(9) ✨

okay so this is a page from the Kernel API Manual — section 9, bestie — and it’s about continue_allocating, which is lowkey a main character in the allocation-search plot. 🎀

---

🌸 NAME 🌸

continue_allocating — continue searching for an allocation by enqueuing to wait for scrubbing or switching to the next zone. 💅

🦋 SYNOPSIS 🦋

bool continue_allocating (struct data_vio *data_vio );

🎀 ARGUMENTS 🎀

• data_vio — the data_vio attempting to get an allocation. 🫶

💖 DESCRIPTION 💖

vibe check, bestie: this method should only be called from the error handler set in data_vio_allocate_data_block.

That’s the whole rule, and it’s not a suggestion — “should only be called” is giving strict-mom energy. 😭 So like, don’t just call it from anywhere; it belongs to the error handler set in data_vio_allocate_data_block, periodt. ✨

🔥 RETURN 🔥

true if the allocation process has continued in another zone. ✅

🌈 SEE ALSO 🌈

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

---

okay that’s the whole page, bestie 🫶 — source/version: ./drivers/md/dm-vdo, date: October 2026, and it’s filed under continue_allocating(9). slay and goodbye 💅✨