launch_data_...cpu_callback(9)

✨ NAME ✨

Okay bestie, welcome to the launch_data_...cpu_callback(9) page from the Kernel API Manual 💖 (yes, the header has that lil ... in it — it’s giving mysterious header energy, we love that for us).

The NAME section is literally: launch_data_vio_cpu_callback — “Set a callback to run on the CPU queues and invoke it immediately.” Periodt, slay ✨

🌸 SYNOPSIS 🌸

void launch_data_vio_cpu_callback (struct data_vio *data_vio , vdo_action_fn callback , enum vdo_completion_priority priority );

🎀 ARGUMENTS 🎀

Not the page leaving us on read 😭 lowkey all three arguments are listed as -- undescribed -- in the original. No cap, that’s the whole mood:

• data_vio — -- undescribed -- 🙈
• callback — -- undescribed -- 🙈
• priority — -- undescribed -- 🙈

🦋 SEE ALSO 🦋

Highkey a whole reading list, iykyk:

• Kernel file ./drivers/md/dm-vdo/data-vio.h
• continue_data_vio_with_error(9)
• launch_data_vio_hash_zone_callback(9)
• launch_data_vio_logical_callback(9)
• launch_data_vio_allocated_zone_callback(9)
• launch_data_vio_duplicate_zone_callback(9)
• launch_data_vio_journal_callback(9)
• launch_data_vio_packer_callback(9)
• launch_data_vio_bio_zone_callback(9)
• launch_data_vio_on_bio_ack_queue(9)

And that’s the whole page, bestie 🫶 it’s from ./drivers/md/dm-vdo, dated October 2026 — mwah 💋