start_scrubbing(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ start_scrubbing(9) ✨

okay so bestie, welcome to start_scrubbing(9) from the Kernel API Manual β€” section 9 of the manual pages, the section where all the kernel-internals lore lives πŸ’… this one's a little callback with a big job and honestly? she's iconic for it πŸŽ€


🌸 NAME 🌸

start_scrubbing β€” Read the current slab's journal from disk now that it has been flushed.

like literally the name says it all: the slab's journal got flushed, and now we go read it off the disk. no cap 😭✨


πŸ¦‹ SYNOPSIS πŸ¦‹

void start_scrubbing (struct vdo_completion *completion );

that's the whole thing. one function, one pointer, zero returns. it's giving "simple but essential" energy 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • completion β€” The scrubber's vio completion. yep, this is the scrubber's vio completion, and it gets passed straight on through πŸ’œ

⭐ DESCRIPTION ⭐

So here's the tea: this callback is registered in scrub_next_slab πŸ”₯

that's it, that's the whole description β€” she's a callback, she's registered in scrub_next_slab, and she shows up when she's needed. main character energy, honestly πŸ‘‘

bestie pls note: that's genuinely all the manpage gives us here β€” I'm not gonna invent extra lore about what she does inside, because that would be lying and we don't do that in this group chat πŸ™ˆ

🌈 SEE ALSO 🌈

okay this is the part where the page absolutely ate β€” there is a Kernel file reference and then a truly enormous list of friends, and we are naming every single one because nobody gets left on read πŸ’–

Kernel file: ./drivers/md/dm-vdo/slab-depot.c

and now, the whole crew, in order, no skips, no cuts ✨

like. that's a whole contact list bestie, and every single one of them is linked πŸ’…πŸ”—


that's the whole page!! πŸ§šβ€β™€οΈ go read some slab-depot source and hydrate, ily πŸ“

signed, sealed, delivered from ./drivers/md/dm-vdo β€” October 2026 β€” start_scrubbing(9) πŸ’–

πŸ“¦ where this page comes from