vdo_start_loading(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… vdo_start_loading(9) β€” like, the Kernel API Manual page, bestie

Okay so real talk: this is vdo_start_loading(9) from the Kernel API Manual, and it's genuinely one of those little functions that decides whether a whole load operation gets to happen. Let's get into it ✨


🌸 NAME 🌸

vdo_start_loading β€” initiate a load operation if the current state permits it. That "if" is doing a lot of work, okay? State said no, the load says no. Periodt.


πŸŽ€ SYNOPSIS πŸŽ€

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

Look at that signature. Four arguments, returns a bool. Clean, iconic, no notes πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • state β€” the current admin state. This is the vibe check right here; the whole question of whether the load can start comes down to what's in here.
  • operation β€” the type of load you're trying to initiate. Gotta be specific, bestie, it's a const struct admin_state_code *.
  • waiter β€” the completion to notify when the load is done, and yes it may be NULL. No waiter, no notification, no drama.
  • initiator β€” the vdo_admin_initiator_fn to call if the operation may begin. Also may be NULL, so like, optional but make it make sense.

⭐ RETURN ⭐

Returns true if the load was initiated πŸŽ‰ If it wasn't, the waiter gets notified instead β€” so either way somebody's getting a callback, fr fr.


πŸ”₯ SEE ALSO πŸ”₯

Everything lives in the kernel file ./drivers/md/dm-vdo/admin-state.c, and honestly the whole friend group is here:


Go read the whole crew in admin-state.c if you wanna understand the state machine arc. It's giving main character energy, ngl 🫢

And that's the page, babe πŸ’– Signing off from ./drivers/md/dm-vdo, dated October 2026 β€” see you in the next vdo_start_loading(9) cameo, mwah πŸŽ€βœ¨

πŸ“¦ where this page comes from