vdo_submit_m...ata_vio_wait(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’œ vdo_submit_m...ata_vio_wait(9) β€” the Kernel API Manual, bestie edition

okay so real talk, this is vdo_submit_m...ata_vio_wait from the Linux Kernel API manual, and she is lowkey the moment you need when the work queues haven't even been born yet. keep reading, i promise it's giving clutch. ✨


✨ NAME ✨

vdo_submit_metadata_vio_wait β€” submit I/O for a metadata vio and wait for it to complete. yes bestie, the waiting is the whole personality. πŸŽ€


🌸 SYNOPSIS 🌸

int vdo_submit_metadata_vio_wait (struct vio *vio ,
physical_block_number_t physical , blk_opf_t operation );

look at that signature, she ate. πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • vio β€” the vio you're issuing I/O for. that's her, that's the main character. πŸ‘‘
  • physical β€” the physical block number to read from or write to. like, the actual address on disk, no cap. πŸ“
  • operation β€” the type of I/O to perform. what flavour of I/O are we doing today, bestie? πŸ”₯

πŸ’– DESCRIPTION πŸ’–

so this function works basically the same as __submit_metadata_vio, except β€” and this is the important part β€” it blocks until the work is done. like it will literally sit there and wait, fr fr. 😭

it's the one you reach for when you need to do i/o before work queues and thread completions are set up. early-bird energy. 🐣✨


🌈 RETURN 🌈

VDO_SUCCESS or an error. that's it, that's the tea. πŸ“

ngl, always check the return value. VDO_SUCCESS is the slay outcome; anything else means something went sideways. πŸ’€

⭐ SEE ALSO ⭐

kernel file ./drivers/md/dm-vdo/io-submitter.c:

the whole friend group, together again. 🫢


and that's the page! 🧚 shoutout to ./drivers/md/dm-vdo β€” the source/version of this little masterpiece β€” dated October 2026. mwah, iconic, no notes. πŸ’œπŸŒΈ

πŸ“¦ where this page comes from