vdo_prepare_completion(9)

💖 vdo_prepare_completion(9) — Kernel API Manual, but make it group chat 💖

🦋 NAME 🦋

vdo_prepare_completion — prepare a completion for launch. ✨

✨ SYNOPSIS ✨

void vdo_prepare_completion (struct vdo_completion *completion , vdo_action_fn callback , vdo_action_fn error_handler , thread_id_t callback_thread_id , void *parent );

🎀 ARGUMENTS 🎀

Okay bestie, the original page is out here giving absolutely zero lore for these, so I’m keeping it 100% honest: every single one is literally marked -- undescribed -- 😭

• completion — -- undescribed -- 🙈
• callback — -- undescribed -- 💀
• error_handler — -- undescribed -- 🫠
• callback_thread_id — -- undescribed -- 🎀
• parent — -- undescribed -- 🌸

No cap, that’s all the manual says about them. I cannot invent extra behavior and call it canon. 💅

💅 DESCRIPTION 💅

So the vibe is: it resets the completion first, and then it sets its callback, error handler, callback thread, and parent. That’s the whole glow-up. ✨

🌈 SEE ALSO 🌈

Kernel file ./drivers/md/dm-vdo/completion.h 👀

• vdo_run_completion(9)
• vdo_reset_completion(9)
• vdo_launch_completion(9)
• vdo_continue_completion(9)
• vdo_fail_completion(9)
• vdo_assert_completion_type(9)
• vdo_launch_completion_callback(9)
• vdo_prepare_completion_for_requeue(9)

okay bye bestie 🫶 this iconic little page comes from ./drivers/md/dm-vdo, is dated October 2026, and belongs to vdo_prepare_completion(9). periodt. 💖