vdo_assert_completion_type(9)

💅 vdo_assert_completion_type 💅

okay so bestie, welcome to the vdo_assert_completion_type(9) page — yes that's a kernel API manual, yes we're doing this, and yes it's gonna slay 🫶

---

🌸 NAME 🌸

vdo_assert_completion_type — literally just asserts that a completion is of the correct type. that's it. that's the whole vibe check ✨

---

🎀 SYNOPSIS 🎀

int vdo_assert_completion_type (struct vdo_completion *completion , enum
vdo_completion_type expected );

like, you hand it a completion and the expected type, and it checks the vibes match 💖

---

🦋 ARGUMENTS 🦋

okay so about these two… the original page is out here giving us nothing 😭 both are straight-up marked -- undescribed --, so no cap, we genuinely don't have descriptions for them. i'm not gonna make stuff up, that's not the move 🙈

• completion — -- undescribed -- (the manual really said "figure it out" 💀)
• expected — -- undescribed -- (same energy, iconic of it honestly)

ngl bestie, if you need the real tea on these params, the source is your bestie — not this page 💜

---

⭐ RETURN ⭐

Returns VDO_SUCCESS or an error. that's the whole spectrum, lowkey 🍓

---

🔥 SEE ALSO 🔥

Kernel file ./drivers/md/dm-vdo/completion.h, plus the whole completion friend group — go say hi 👑:

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

---

🌈 and that's the page!! this little icon came out of ./drivers/md/dm-vdo, dated October 2026, and it goes by vdo_assert_completion_type(9) — mwah, go assert some types, ily, bye 💅✨🎀