vdo_start_resuming(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… vdo_start_resuming(9) β€” the Kernel API Manual glow-up πŸŽ€

okay so bestie, welcome to vdo_start_resuming(9) from the Kernel API Manual β€” this is the little function that's like "hey, can we resume rn? if the vibe check passes, let's GO" ✨


🌸 NAME 🌸

vdo_start_resuming β€” initiate a resume operation if the current state permits it. that's it, that's the whole pitch πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

bool vdo_start_resuming (struct admin_state *state , const struct
admin_state_code *operation , struct vdo_completion *waiter ,
vdo_admin_initiator_fn initiator );

literally the whole signature, no cap β€” copy it exactly or the compiler will absolutely come for you 😭


✨ ARGUMENTS ✨

  • state β€” the current admin state. the main character of this whole thing, fr fr πŸ‘‘
  • operation β€” the type of resume to start. like, which flavor of resume are we doing πŸ“
  • waiter β€” the completion to notify when the resume is complete; may be NULL. yes bestie, NULL is allowed, it's giving low-maintenance πŸ™ˆ
  • initiator β€” the vdo_admin_initiator_fn to call if the operation may begin; may be NULL. also optional, also unbothered πŸ’…

πŸ”₯ RETURN πŸ”₯

returns true if the resume was initiated πŸŽ‰ β€” and if not, the waiter will be notified instead. so like, either way somebody's getting a message, don't worry 🫢


🌈 SEE ALSO 🌈

the kernel file is ./drivers/md/dm-vdo/admin-state.c β€” that's where the magic lives, screenshot it πŸ“Έ

and here's the whole friend group, all of them, in order:


ok that's the whole page bestie, every argument, every return value, every single SEE ALSO β€” nothing dropped, we ate and left no crumbs πŸ’€βœ¨

and that's a wrap on this one, brought to you by ./drivers/md/dm-vdo β€” October 2026 edition πŸ—“οΈπŸ’œ mwah, go forth and resume responsibly πŸ§šβ€β™€οΈ

πŸ“¦ where this page comes from