write_bio_finished(9)

✨ write_bio_finished(9) ✨

okay so this is the write_bio_finished(9) page from the Kernel API Manual, and honestly? it's a little one but it's iconic. it's the bio_end_io function, right, and it gets registered in write_block() so it can be called once a data_vio's write to the underlying storage has finished. that's the whole vibe. 💅

🌸 SYNOPSIS 🌸

void write_bio_finished (struct bio *bio );

like yes that's it, that's the whole signature, no cap 🫶

🎀 ARGUMENTS 🎀

• bio — the bio to update. that's it, that's the assignment bestie 💖

🦋 SEE ALSO 🦋

the whole friend group, in order, fr fr:

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), update_block_map(9), read_old_block_mapping(9), pack_compressed_data(9), compress_data_vio(9), launch_compress_data_vio(9), hash_data_vio(9), acknowledge_write_callback(9), allocate_block(9), handle_allocation_error(9), continue_data_vio_with_block_map_slot(9)

that's the page!! short and sweet, main character energy honestly 👑

source: ./drivers/md/dm-vdo · October 2026 · write_bio_finished(9) — mwah, love u, go read the rest of the dm-vdo lore 🍓🧚💜