libnvme(9)

💅 libnvme(9) — ok bestie, let's talk about this enum

So you opened the libnvme(9) API Manual page and it's just… an enum. A whole little enum. And honestly? It ate. Let's get into it 🎀

---

✨ NAME ✨

enum nvme_feat_nswpcfg_state — the Write Protection - Write Protection State situation. That's the whole vibe: it's the list of states that NVMe namespace write protection can be in. No cap, that's literally it 🦋

---

🌸 SYNOPSIS 🌸

Here's the whole thing, exactly as it lives in the header, bestie — don't let anyone tell you it's more complicated than this:

enum nvme_feat_nswpcfg_state {
    NVME_FEAT_NS_NO_WRITE_PROTECT ,
    NVME_FEAT_NS_WRITE_PROTECT ,
    NVME_FEAT_NS_WRITE_PROTECT_PWR_CYCLE ,
    NVME_FEAT_NS_WRITE_PROTECT_PERMANENT

};

Look at her. Four constants, all iconic, all with a little trailing comma situation before the brace. We respect it 💜

---

👑 Constants 👑

Okay so these are the four states you can be in, and each one has its own energy. Let me introduce you 💅

• NVME_FEAT_NS_NO_WRITE_PROTECT — the main character state: No Write Protect. Nothing's locked, everything's writable, live your life 🌈
• NVME_FEAT_NS_WRITE_PROTECT — Write Protect. Yep. She's protected. The writes are not coming through, iykyk 🔥
• NVME_FEAT_NS_WRITE_PROTECT_PWR_CYCLE — Write Protect Until Power Cycle. Temporarily locked down — a power cycle and she's free again. It's giving "brb gotta reboot my boundaries" ⭐
• NVME_FEAT_NS_WRITE_PROTECT_PERMANENT — Permanent Write Protect. The forever one. Lowkey scary, highkey serious — this state does not undo itself 💀

fr fr, read the last two names carefully before you go flipping states around. They are not the same vibe and the manual is very clear about that 🙈

---

And that's the page, bestie! 🫶 Straight from the enum nvme_feat_nswpcfg_state section of the libnvme(9) API Manual, dated October 2026 — catch you on the next manpage, mwah 💖✨🎀