modify_for_partial_write(9)

💅 modify_for_partial_write(9) 💅

okay bestie, welcome to the Kernel API Manual, section 9 — this page is literally all about modify_for_partial_write, and it’s giving “small callback, important job” energy. 🦋

✨ NAME ✨

modify_for_partial_write — does the modify-write part of a read-modify-write cycle. no cap, that’s the whole name vibe. 🎀

🌸 SYNOPSIS 🌸

void modify_for_partial_write (struct vdo_completion *completion );

💖 ARGUMENTS 💖

• completion — the data_vio that just finished its read. yep, that’s the one you’re handing over, bestie. 🫶

🦋 DESCRIPTION 🦋

This callback is registered in read_block. fr fr, that’s the described behavior — it’s the callback that gets registered there. 💅

🌈 SEE ALSO 🌈

The kernel file is ./drivers/md/dm-vdo/data-vio.c, and the see-also squad is:

• 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)
• 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)
• write_bio_finished(9)
• acknowledge_write_callback(9)
• allocate_block(9)
• handle_allocation_error(9)
• continue_data_vio_with_block_map_slot(9)

okay that’s the page, bestie 💖 — straight from ./drivers/md/dm-vdo, dated October 2026, and it’s modify_for_partial_write(9). periodt 🫶