update_block_map(9)

okay so bestie, this is the Kernel API Manual page for update_block_map(9) — yes, we’re in the kernel docs and she’s lowkey iconic ✨

💅 NAME 💅

update_block_map — this is the rendezvous of the data_vio and decrement completions, after each one has made its reference updates. Handle any error from either of them, or proceed to updating the block map. That’s the whole assignment, no cap 💖

✨ SYNOPSIS ✨

void update_block_map (struct vdo_completion *completion );

🫶 ARGUMENTS 🫶

• completion — the completion of the write in progress. That’s it, that’s the parameter 🎀

💖 SEE ALSO 💖

the whole squad, every single one, no skipping 💅

• Kernel file ./drivers/md/dm-vdo/data-vio.c
• Bio flags.(9)
• Introduction(9)
• check_for_drain_complete_locked(9)
• pack_status(9)
• set_data_vio_compression_status(9)
• cancel_data_vio_compression(9)
• attempt_logical_block_lock(9)
• launch_data_vio(9)
• schedule_releases(9)
• process_release_callback(9)
• initialize_data_vio(9)
• make_data_vio_pool(9)
• free_data_vio_pool(9)
• vdo_launch_bio(9)
• drain_data_vio_pool(9)
• resume_data_vio_pool(9)
• dump_data_vio_pool(9)
• release_allocated_lock(9)
• release_logical_lock(9)
• finish_cleanup(9)
• get_data_vio_operation_name(9)
• data_vio_allocate_data_block(9)
• release_data_vio_allocation_lock(9)
• uncompress_data_vio(9)
• modify_for_partial_write(9)
• read_block(9)
• read_old_block_mapping(9)
• pack_compressed_data(9)
• compress_data_vio(9)
• launch_compress_data_vio(9)
• hash_data_vio(9)
• write_bio_finished(9)
• acknowledge_write_callback(9)
• allocate_block(9)
• handle_allocation_error(9)
• continue_data_vio_with_block_map_slot(9)

xoxo, bestie 💖 — source/version: ./drivers/md/dm-vdo · date: October 2026 · update_block_map(9) and out 🎀