grow_physical_callback(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… grow_physical_callback(9) β€” Kernel API Manual, section 9 πŸŽ€

okay so bestie, welcome to the Kernel API Manual, section 9, and today's main character is grow_physical_callback. she's the one who kicks off a grow physical. that's it, that's the plot ✨


🌸 NAME 🌸

grow_physical_callback β€” the callback that initiates a grow physical. she shows up, she starts the thing. iconic behavior honestly πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

void grow_physical_callback (struct vdo_completion *completion );

note the void β€” she returns nothing, she's not here to give you answers, she's here to start stuff. πŸ”₯


πŸŽ€ ARGUMENTS πŸŽ€

  • completion β€” the admin completion. that's the whole vibe. that's the parameter. struct vdo_completion pointer, and it's the admin one, no cap 🫢

πŸ’– DESCRIPTION πŸ’–

so basically: this callback is registered in perform_grow_physical. that's the whole description, and honestly? she said what she said. short, sweet, registered. ⭐

lowkey the shortest DESCRIPTION ever and I respect it so much 😭

πŸ”₯ SEE ALSO πŸ”₯

the friend group. the whole group chat. and yes, you're gonna read all of them, because I said so πŸ’œ

the kernel file ./drivers/md/dm-vdo/dm-vdo-target.c, plus:

like, the whole dm-vdo extended universe is in here 🧚


and that's the page!! πŸ’« huge thanks to the source at ./drivers/md/dm-vdo, dated October 2026 β€” mwah, love you, mean it πŸ«ΆπŸ’–πŸŽ€

πŸ“¦ where this page comes from