vdo_dump_slab_depot(9)

📦 version 7.3.1, in nixpkgs unstable

💖 vdo_dump_slab_depot(9) — Kernel API Manual 💖

okay bestie, welcome to the vdo_dump_slab_depot(9) page, straight out of the Kernel API Manual. yes, we're in kernel-land. yes, there will be headers. stay with me 🫶

✨ NAME ✨

vdo_dump_slab_depot — dump the slab depot, in a thread-unsafe fashion.

that's it. that's the whole vibe. but read the fine print below because "thread-unsafe" is doing a lot of heavy lifting there 👀

✨ SYNOPSIS ✨

void vdo_dump_slab_depot (const struct slab_depot *depot );

literally one (1) function call, no return value, zero drama. she's void, she takes one pointer, she's done 💅

🌸 ARGUMENTS 🌸

  • depot — the slab depot. that's the whole description. yes, really. the slab depot is the thing you pass, and you pass the slab depot. iconic circular queen 👑
💀 heads up babe: this is thread-unsafe. the original says so right in the NAME line. so like… don't be out here calling this from five threads at once and then acting surprised. iykyk.

🦋 SEE ALSO 🦋

okay so this is the part where the page just goes feral and lists, no joke, the entire cast of ./drivers/md/dm-vdo/slab-depot.c. grab a snack, this is a long credits roll 🎬✨

and if you want the actual source of all this lore, it lives in the kernel file ./drivers/md/dm-vdo/slab-depot.c. go read it, i believe in you 🌈

🎀 that's the whole page bestie. no bugs section, no return value section, no examples — the depot got dumped and we're moving on. periodt.

mwah 💋 this little writeup came to you from ./drivers/md/dm-vdo, dated October 2026, and it's the vdo_dump_slab_depot(9) page — go forth and dump responsibly, thread-safely, and never on a Friday deploy 🧚✨

📦 where this page comes from