vdo_get_com...ock_fragment(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… vdo_get_com...ock_fragment(9) β€” like, the Kernel API Manual page, bestie ✨

okay so this is one of those Kernel API Manual pages πŸŽ€ and honestly? it's short, it's sweet, and it's gonna make sense in like two minutes fr fr. let's go πŸ¦‹


✨ NAME ✨

vdo_get_compressed_block_fragment β€” get a reference to a compressed fragment from a compressed block πŸ’–

🌸 SYNOPSIS 🌸

int vdo_get_compressed_block_fragment (enum block_mapping_state
mapping_state , struct compressed_block *block , u16 *fragment_offset ,
u16 *fragment_size );

like yes the spacing is a little quirky, that's just how it is, don't come for me πŸ™ˆ

🫢 ARGUMENTS 🫢

  • mapping_state β€” the mapping state that's describing the fragment, iykyk πŸ‘‘
  • block β€” the compressed block that was read from disk. it came from disk, bestie, respect it πŸ’€
  • fragment_offset β€” the offset of the fragment within the compressed block πŸ“
  • fragment_size β€” and this one's the size of the fragment, periodt ✨

πŸ’œ RETURN πŸ’œ

if a valid compressed fragment is found, you get VDO_SUCCESS πŸŽ‰ slay.

otherwise you get VDO_INVALID_FRAGMENT if the fragment is invalid 😭 β€” so, y'know, vibe check the return value, please 🌈

πŸ”₯ SEE ALSO πŸ”₯

okay this is the part where it goes full group-chat-tag-everyone energy 🌸 β€” the Kernel file ./drivers/md/dm-vdo/packer.c and honestly a whole cast:

like, that's the whole packer friend group, no cap πŸ’…


ok and finally the cute lil sign-off: this one lives in ./drivers/md/dm-vdo, dated October 2026, and it's page vdo_get_com...ock_fragment(9) of the Kernel API Manual πŸŽ€ mwah, go read your man pages bestie πŸ’–πŸ¦‹
πŸ“¦ where this page comes from