vdo_get_phys...one_pbn_lock(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, welcome to the Kernel API Manual page called vdo_get_phys...one_pbn_lock(9) β€” yes, the title is literally doing the ellipsis thing, and the actual function is vdo_get_physical_zone_pbn_lock. She's specific, she's iconic, and we're gonna get through every single detail together πŸ’…βœ¨

πŸ’– NAME πŸ’–

vdo_get_physical_zone_pbn_lock β€” get the lock on a PBN if one exists. That's the whole name-vibe: if there's a lock, you get it; if there isn't, you don't. Periodt.

✨ SYNOPSIS ✨

Here's the signature, bestie β€” copy it exactly, no freestyling:

struct pbn_lock * vdo_get_physical_zone_pbn_lock (struct physical_zone
       *zone , physical_block_number_t pbn );

πŸŽ€ ARGUMENTS πŸŽ€

  • zone β€” the physical zone responsible for the PBN. Like, the zone that's responsible for this block number, okay?
  • pbn β€” the physical block number whose lock is desired. You want the lock for this pbn, and you're asking nicely.

πŸ¦‹ RETURN πŸ¦‹

You get the lock, or NULL if the PBN is not locked. That's the whole return situation β€” lock if locked, NULL if not locked, no cap.

🌈 SEE ALSO 🌈

This all lives in the Kernel file ./drivers/md/dm-vdo/physical-zone.c, and here's the whole friend group β€” every single one, because we do not skip the squad:


okay bye bestie 🫢 this page's footer says source/version ./drivers/md/dm-vdo, dated October 2026, with the footer title vdo_get_phys...one_pbn_lock(9) β€” slay and goodnight πŸ’–πŸ‘‘

πŸ“¦ where this page comes from