launch_data...one_callback(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… launch_data...one_callback(9) β€” like, the actual name is launch_data_vio_duplicate_zone_callback

okay so bestie, welcome to the Kernel API Manual πŸŽ€ β€” yes, that's the manual name, and yes, we're doing kernel internals today. Buckle up, it's giving "3am in drivers/md" energy and honestly? iconic.


✨ NAME ✨

launch_data_vio_duplicate_zone_callback β€” sets a callback as a physical block operation in a data_vio's duplicate zone, then queues the data_vio and invokes it immediately. Like, all of it. Right away. No waiting around, no "let me think about it" β€” it's main character energy, it just goes. πŸ”₯

ngl the "invoke it immediately" part is doing a lot of heavy lifting in that sentence, so don't sleep on it.

✨ SYNOPSIS ✨

void launch_data_vio_duplicate_zone_callback (struct data_vio *data_vio
, vdo_action_fn callback );

That's the whole thing. Returns void, so don't go looking for a return value, there isn't one πŸ’€


✨ ARGUMENTS ✨

  • data_vio β€” a struct data_vio *... and that's genuinely all we get, bestie. The manual says undescribed. Not me being lazy β€” the source page literally just doesn't describe it. πŸ™ˆ
  • callback β€” a vdo_action_fn... also marked undescribed. Same story. The docs said "figure it out" and honestly? relatable. 😭
fr fr, both arguments are listed as -- undescribed -- in the original. I'm telling you that on purpose so you don't think I skipped a section. Nothing was skipped. There was just nothing there. πŸ’€

✨ SEE ALSO ✨

πŸ¦‹ the source file

  • Kernel file ./drivers/md/dm-vdo/data-vio.h β€” like, the whole dm-vdo directory lives at ./drivers/md/dm-vdo, and this is the header you want.

🫢 the sibling callbacks (yes, it's a whole friend group)

like, that's nine whole references β€” the duplicate-zone one is literally part of a set, a little squad of launch_data_vio_*_callback functions all doing their own zone thing. collect them all, iykyk ✨


🌸 the cute sign-off 🌸

This page is brought to you by ./drivers/md/dm-vdo (that's the source, and also the version line, they're the same thing here, don't @ me) and it's dated October 2026 β€” so yes, the docs are from the future, slay πŸ‘‘. Same title, same section (9), both corners nice and tidy. πŸ’–

periodt. now go read data-vio.h, bestie. πŸ’…πŸ¦‹

πŸ“¦ where this page comes from