continue_parent(9)

💅 continue_parent(9) — from the Kernel API Manual, bestie

okay so we're diving into continue_parent(9) and honestly? it's a whole little moment in the kernel. this one lives in the Kernel API Manual (yes, the (9) means kernel API docs, iykyk), and it's about picking a save operation back up where its parent left off. short page, big "the way that…" energy. let's get into it 🎀

---

✨ NAME ✨

continue_parent — Continue the parent of a save operation. periodt. that's the whole vibe. it continues the parent. of a save operation. no notes 💅

---

🌸 SYNOPSIS 🌸

void continue_parent (struct vdo_completion *completion );

look at her. one parameter, returns nothing (void), takes a pointer to a struct vdo_completion. she's simple, she's iconic, she's literally one line 🦋

---

🫶 ARGUMENTS 🫶

• completion — The completion to continue. that's it. that's the argument. hand her the completion and she continues it ✨

---

👑 SEE ALSO 👑

okay bestie, buckle up, because this list is long and honestly it's giving "the whole friend group showed up to the party" 🌈 every single one of these is part of the saga — same section of the kernel, same story arc. no cap, i'm listing all of them 💖

First up, the home base:

• Kernel file ./drivers/md/dm-vdo/vdo.c Introduction(9)

and then, in the order they appear, the whole crew:

• 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)
• 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)

like, fifty-something cross-references, but who's counting (me, i counted, i'm obsessed) 🔥 go read them, they're all right there in ./drivers/md/dm-vdo 💜

---

ngl, the whole page is basically three lines of actual API and then the longest SEE ALSO in the group chat. love that for us. no invented lore, no extra tips — just what the page says, slayed and delivered 🧚

---

and that's the page, bestie ✨ this little gem comes from the source tree at ./drivers/md/dm-vdo, and it's dated October 2026 — so yeah, she's from the future and she's still just continuing parents 💖🎀🦋 bye bestie, go continue something 🫶