create_mult...metadata_vio(9)

📦 version 7.3.1, in nixpkgs unstable

🦋 create_mult...metadata_vio(9) — like, the Kernel API Manual bestie era 🎀

okay so this is one of those kernel API pages from the Kernel API Manual, and it's lowkey a builder function — it literally makes a vio for you. icon behaviour honestly. let's get into it 💅

✨ NAME ✨

create_multi_block_metadata_vio — Create a vio. that's it, that's the whole vibe 🫶

🌸 SYNOPSIS 🌸

int create_multi_block_metadata_vio (struct vdo *vdo , enum vio_type
vio_type , enum vio_priority priority , void *parent , unsigned int
block_count , char *data , struct vio **vio_ptr );

💖 ARGUMENTS 💖

  • vdo — The vdo on which the vio will operate. it's the main character of this whole story ngl 👑
  • vio_type — The type of vio to create. so, like, which flavour of vio we're making 🍓
  • priority — The relative priority to assign to the vio. yes bestie, this one gets a priority ✨
  • parent — The parent of the vio. found family fr fr 🫶
  • block_count — The size of the vio in blocks. how big, basically 💀
  • data — The buffer. the actual data moment 🌈
  • vio_ptr — A pointer to hold the new vio. it's giving "here's an empty spot, put the baby vio in it" 🥹

⭐ RETURN ⭐

VDO_SUCCESS or an error. slay or 😭, there is no in-between.

🔥 SEE ALSO 🔥

the kernel file lives at ./drivers/md/dm-vdo/vio.c — go be nosy, iykyk 👀

and the whole friend group shows up too:

ngl this one's short and sweet — but do NOT skip the error case, VDO_SUCCESS is not guaranteed and that's just how it is 💀

kisses bestie 💋 this page came from ./drivers/md/dm-vdo and it's dated October 2026 — mark your calendar, periodt. 🎀🧚‍♀️

📦 where this page comes from