ceph_cls_break_lock(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ceph_cls_break_lock — the kernel API manual, bestie edition

Okay so real talk, this is ceph_cls_break_lock(9), and yes the manual name is lowkey part of the title because that's just how manpages roll. Buckle up 🎀

✨ NAME ✨

ceph_cls_break_lock — release rados lock for object for specified client 🦋

Like, it breaks a lock. On purpose. For a specific client. That's the whole vibe.

🔥 SYNOPSIS 🔥

int ceph_cls_break_lock (struct ceph_osd_client *osdc , struct
ceph_object_id *oid , struct ceph_object_locator *oloc , char *lock_name
, char *cookie , struct ceph_entity_name *locker );

It returns an int, it takes six things, and it's giving "I know exactly what I'm doing" main character energy 👑

🌸 ARGUMENTS 🌸

  • osdc — the OSD client instance. Your whole ✨connection moment✨ to the thing that actually holds the data.
  • oid — object to lock. Which object are we talking about? This one. 🫶
  • oloc — object to lock. (Yes bestie, the manual literally says the same thing as oid. Not me double-checking. That's just what it says. 💀)
  • lock_name — the name of the lock. Gotta know what you're breaking, iykyk.
  • cookie — user-defined identifier for this instance of the lock. It's the lock's little name tag 🎀
  • locker — current lock owner. The one currently holding it down. We're here to relieve them of duty 😭

👀 SEE ALSO 👀

Kernel file ./net/ceph/cls_lock_client.c — that's where the actual lore lives, fr fr.

Go read those too, they're the platonic ideal of "same friend group, different function" 💜

ngl, if you're breaking locks you better know you're supposed to. This is a kernel API, not a vibes-only situation. Lock discipline is iconic when done right and catastrophic when done wrong 🙈

Okay that's the whole page, no notes. Sourced from ./net/ceph, dated October 2026, and it's literally called ceph_cls_break_lock(9) — slay, go forth and unlock responsibly 💅✨

📦 where this page comes from