vdo_assert_o..._zone_thread(9)

💖 vdo_assert_o..._zone_thread(9) 💖

okay so bestie, welcome to the kernel API manual — this one's called vdo_assert_o..._zone_thread(9) (yes the name is abridged, that's just how the page header rolls, no cap). it lives in the Kernel API Manual and honestly? it's giving tiny-but-mighty. ✨

---

🌸 NAME 🌸

vdo_assert_on_physical_zone_thread — the function that straight-up asserts you called it on the specified physical zone thread. like a vibe check but for threads, fr fr.

---

🦋 SYNOPSIS 🦋

void vdo_assert_on_physical_zone_thread (const struct vdo *vdo ,
zone_count_t physical_zone , const char *name );

she takes three args and returns nothing (void, queen of not giving anything back 💅). copy it exactly like that, spacing and all — iykyk.

---

🎀 ARGUMENTS 🎀

• vdo — the vdo. that's it, that's the description. the vdo. iconic minimalism honestly 👑
• physical_zone — the number of the physical zone 🌀
• name — the name of the calling function. so when someone asks "who called this", you already know 🫶

---

💜 SEE ALSO 💜

so there's kind of a lot here — this page travels in a big group chat. first up, the kernel file:

./drivers/md/dm-vdo/vdo.c — and Introduction(9), your lil entry point 🌈

then the whole friend group, in order, no skipping (i promised i'd keep every single one and i meant it):

• 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_synchronous_flush(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_get_physical_zone(9)

like i said. huge friend group. read them all, they're literally all relevant 🍓

ok and one last thing before you go — this page is chillin' in ./drivers/md/dm-vdo, dated October 2026, and it signs off as vdo_assert_o..._zone_thread(9). so like… future vibes 🌸✨ mwah, go assert some threads bestie 🧚💖