retry_allocation(9)

okay bestie, welcome to retry_allocation(9) from the Kernel API Manual ✨ This page is short and iconic: it’s about retrying the allocation of a block now that we’re done waiting for scrubbing. Lowkey a little “finally, my turn” moment, and we’re obsessed. 💅

💖 NAME 💖

retry_allocation — retry allocating a block now that we’re done waiting for scrubbing. That’s the whole vibe. No cap. 🫶

✨ SYNOPSIS ✨

void retry_allocation (struct vdo_waiter *waiter , void *context );

Literally that signature, character for character, bestie. It returns void, so there’s no return value to catch. 💀

🌸 ARGUMENTS 🌸

• waiter — the allocating_vio that was waiting to allocate. The one that was waiting to allocate, periodt. 🎀
• context — the context (unused). Not me pointing out that it’s unused, but yeah — it’s unused. 🙈

🦋 SEE ALSO 🦋

Kernel file ./drivers/md/dm-vdo/physical-zone.c — yes, that’s the source-file bestie for this whole situation. 🌈

• 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)
• 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. Cute sign-off time: source/version ./drivers/md/dm-vdo, date October 2026, manual retry_allocation(9) — mwah 💋✨