vdo_share_c...d_write_lock(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… vdo_share_compressed_write_lock(9) β€” Kernel API Manual ✨

okay so bestie, welcome to the Kernel API Manual πŸŽ€ β€” this one's from the dm-vdo crew and it's literally the glow-up moment for a lock. buckle up πŸ¦‹


🌸 NAME 🌸

vdo_share_compressed_write_lock β€” the function that takes a data_vio's hash lock and makes it a shared holder of the PBN lock on the compressed block its data just got written to. yes queen, it's upgrading the vibes from exclusive to shared πŸ’–


⭐ SYNOPSIS ⭐

void vdo_share_compressed_write_lock (struct data_vio *data_vio , struct
pbn_lock *pbn_lock );

that's it, that's the whole signature, no cap 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • data_vio β€” the data_vio that just got compressed. main character energy, honestly 🧚
  • pbn_lock β€” the PBN lock sitting on that compressed block. the other half of the duo πŸ’œ

πŸ‘‘ DESCRIPTION πŸ‘‘

so here's the tea β˜• β€” if the lock is still a write lock (and ngl, it will be, if this is the first share), it gets converted into a read lock. slay. ✨

this also reserves a reference count increment for the data_vio. so like, it's not just changing the lock type, it's also calling dibs on a refcount bump. periodt πŸ’…


πŸ”₯ SEE ALSO πŸ”₯

the whole friend group, fr fr β€” go say hi to:

like, the entire dedupe.c cast 😭 go read them all, iykyk πŸ’€


and that's the page, bestie πŸ’– this lil icon lives in ./drivers/md/dm-vdo, dated October 2026, and the header gets truncated to vdo_share_c...d_write_lock(9) because even manpage titles deserve a little mystery πŸ™ˆ see u in the next one πŸŒˆβ­πŸ“

πŸ“¦ where this page comes from