finish_updating(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

finish_updating πŸ’…

okay so bestie, welcome to the finish_updating(9) page from the Kernel API Manual β€” it's giving kernel continuation energy, but make it group chat. Stay with me, it's short and iconic. ✨

✨ NAME ✨

finish_updating β€” process the result of a UDS update performed by the agent for the lock. That's the whole assignment, no cap. πŸ’…

🌸 SYNOPSIS 🌸

void finish_updating (struct vdo_completion *completion );

πŸŽ€ ARGUMENTS πŸŽ€

  • completion β€” the completion of the data_vio that performed the update. That's the one we're handing over. 🫢

πŸ¦‹ DESCRIPTION πŸ¦‹

This continuation is registered in start_querying. Literally that's the tea: it's a continuation, and start_querying is where it gets registered. Keep that in mind and you're slaying. ✨

πŸ’– SEE ALSO πŸ’–

okay, there is a whole friend group of related pages and refs, so let's do the roll call one by one, no skipping:

mwah πŸ’‹ β€” source/version: ./drivers/md/dm-vdo, date: October 2026, page: finish_updating(9).

πŸ“¦ where this page comes from