libnvme(9)

💅 libnvme(9) — API Manual, bestie edition

Okay so this is a page straight out of the libnvme API manual — yes, that libnvme(9), the manual name is literally in the corner and I'm putting it right here near the top so you're not confused. It's a tiny one today: one enum, three constants, zero drama. Let's go 🫶

---

✨ NAME ✨

enum libnvme_sed_lock_state — the lock state of a locking range. That's it, that's the whole vibe. It's giving "small but crucial" 🔥

---

🦋 SYNOPSIS 🦋

enum libnvme_sed_lock_state {
    LIBNVME_SED_LOCK_RO ,
    LIBNVME_SED_LOCK_RW ,
    LIBNVME_SED_LOCK_LK

};

Not me presenting the enum like it's a lineup 😭 Three members, that's the whole squad:

---

🎀 Constants 🎀

So these are the three states, and honestly you just need to know which one locks what. Here's the tea ☕:

• LIBNVME_SED_LOCK_RO — read-only, which means writes are locked. You can look, you cannot touch. Window shopping energy 🙈
• LIBNVME_SED_LOCK_RW — read-write, and the range is unlocked. Full access, main character permissions, no cap ✨
• LIBNVME_SED_LOCK_LK — reads and writes are locked. Like, both. Everything. Locked locked. Periodt 💅

Note bestie: LIBNVME_SED_LOCK_RO locks only the writes, LIBNVME_SED_LOCK_LK locks reads and writes — do not mix those two up, iykyk 👑

---

🌸 Sign-off 🌸

And that's the page! This icon was living in the libnvme(9) API Manual, under enum libnvme_sed_lock_state, dated October 2026 — so screenshot the date if you need it for whatever grown-up reason you need it for 🎀 Bye bestie, go lock some ranges responsibly 💖