vdo_downgrad...n_write_lock(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… vdo_downgrade_pbn_write_lock β€” the Kernel API Manual glow-up ✨

okay bestie, welcome to the Kernel API Manual entry for vdo_downgrade_pbn_write_lock(9) β€” yes the title gets abbreviated all cute as vdo_downgrad...n_write_lock(9), that's just how the man page wears its name πŸŽ€


🌸 NAME 🌸

vdo_downgrade_pbn_write_lock β€” it literally downgrades a PBN write lock into a PBN read lock. that's the whole vibe. no cap. πŸ”₯


✨ SYNOPSIS ✨

void vdo_downgrade_pbn_write_lock (struct pbn_lock *lock , bool compressed_write );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • lock β€” the PBN write lock you're downgrading, bestie. that's the one. the main character of this operation πŸ‘‘
  • compressed_write β€” a bool. it's True if the block that got written was a compressed block. literally just tells you whether compression was involved 🫢

πŸ’– DESCRIPTION πŸ’–

so here's the tea β˜• β€” the lock holder count gets cleared. that's it, that's the move. and then? the caller is responsible for setting the new count. not the function, not the kernel, you. the caller. that's on you, babe πŸ˜­πŸ’…


🌈 SEE ALSO 🌈

the whole friend group, fr fr β€” and heads up, these all live in the kernel file ./drivers/md/dm-vdo/physical-zone.c 🧚

like, that's the entire group chat and they ALL ate πŸ’€πŸ”₯


πŸŽ€ the sign-off πŸŽ€

this lil beauty comes to you from ./drivers/md/dm-vdo, dated October 2026 β€” and the page answers to vdo_downgrad...n_write_lock(9) if you ever need to find it again. go off, king. periodt. πŸ’œβ­πŸ“

πŸ“¦ where this page comes from