data_vio_all...e_data_block(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

data_vio_allocate_data_block β€” allocate a data block. Okay bestie, this one is straight out of the Kernel API Manual, and it’s giving β€œsmall function, very important job” energy πŸ’…βœ¨


✨ SYNOPSIS ✨

void data_vio_allocate_data_block (struct data_vio *data_vio , enum
pbn_lock_type write_lock_type , vdo_action_fn callback , vdo_action_fn
error_handler );

πŸŽ€ ARGUMENTS πŸŽ€

  • data_vio β€” the data_vio. Like, the actual one we’re working with here 🫢
  • write_lock_type β€” the type of write lock to obtain on the block. So it’s specifying which write-lock situation we’re getting into πŸ”’
  • callback β€” the callback which will attempt an allocation in the current zone and continue if it succeeds. It’s the β€œtry it in this zone, keep moving if it works” callback ✨
  • error_handler β€” the handler for errors while allocating. The β€œif this goes sideways, call this” bestie 😭

πŸ”₯ SEE ALSO πŸ”₯

Okay, the whole cross-reference squad is here β€” don’t skip a single one, bestie:


That’s a wrap, bestie! Source/version: ./drivers/md/dm-vdo Β· date: October 2026 Β· page: data_vio_all...e_data_block(9). Go forth and allocate πŸ’…βœ¨πŸ¦‹

πŸ“¦ where this page comes from