vdo_synchronous_flush(9)
π vdo_synchronous_flush β like, the Kernel API Manual page, bestie β¨
okay so picture this: it's giving kernel API manual energy, it's a <pink>(9)</> page, and the whole personality is "flush it and wait". Let's go π«Ά
πΈ NAME πΈ
vdo_synchronous_flush β issue a flush request and wait for it to complete. yeah. that's the whole job. it flushes, it waits, it slays π
β¨
π SYNOPSIS π
int vdo_synchronous_flush (struct vdo *vdo );
literally just hand it a vdo and it gives you back an int. no cap.
π¦ ARGUMENTS π¦
vdoβ the vdo. that's it. that's the argument. the vdo in question. iconic, honestly π
β RETURN β
VDO_SUCCESS or an error. so like... it either ate or it didn't, and you'll know which π₯
fr fr check that return value, bestie β VDO_SUCCESS is the good ending, an error means something went sideways π
π SEE ALSO π
the way this list is long and I respect it so much β every single one, coming right up, no skipping, periodt:
- Kernel file
./drivers/md/dm-vdo/vdo.cIntroduction(9) vdo_initialize_device_registry_once(9)filter_vdos_locked(9)vdo_find_matching(9)initialize_thread_config(9)get_thread_name(9)vdo_make_thread(9)register_vdo(9)vdo_format(9)initialize_vdo(9)vdo_make(9)free_listeners(9)unregister_vdo(9)vdo_destroy(9)finish_reading_super_block(9)handle_super_block_read_error(9)vdo_load_super_block(9)vdo_get_backing_device(9)vdo_get_device_name(9)vdo_get_state(9)vdo_set_state(9)vdo_get_admin_state(9)record_vdo(9)continue_parent(9)handle_geometry_block_save_error(9)vdo_save_geometry_block(9)handle_super_block_save_error(9)vdo_save_super_block(9)vdo_save_components(9)vdo_register_read_only_listener(9)notify_vdo_of_read_only_mode(9)vdo_enable_read_only_entry(9)vdo_wait_until_not_entering_read_only_mode(9)as_notifier(9)finish_entering_read_only_mode(9)make_thread_read_only(9)vdo_allow_read_only_mode_entry(9)vdo_enter_read_only_mode(9)vdo_is_read_only(9)vdo_in_read_only_mode(9)vdo_in_recovery_mode(9)vdo_enter_recovery_mode(9)complete_synchronous_action(9)perform_synchronous_action(9)set_compression_callback(9)vdo_set_compressing(9)vdo_get_compressing(9)vdo_get_physical_blocks_allocated(9)vdo_get_physical_blocks_overhead(9)get_vdo_statistics(9)vdo_fetch_statistics_callback(9)vdo_fetch_statistics(9)vdo_get_callback_thread_id(9)vdo_dump_status(9)vdo_assert_on_admin_thread(9)vdo_assert_on_logical_zone_thread(9)vdo_assert_on_physical_zone_thread(9)vdo_get_physical_zone(9)
π and that's the page!! mwah π this lil darling lives in ./drivers/md/dm-vdo, dated October 2026, and it's part of the Kernel API Manual β go read the source, ily, bye π§ββοΈπ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms