libnvme(2)

✨ NAME ✨

enum nvme_feat_nswpcfg_state — Write Protection - Write Protection State

Okay bestie, this is a page straight out of the libnvme API manual (that's libnvme(2), for the girlies taking notes 💅), and it's all about one tiny little enum that tells your NVMe namespace how protected it is. Spoiler: there are four levels of "hands off my data" and one of them is forever. 🫶

---

🌸 SYNOPSIS 🌸

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, one vibe. ✨

---

👑 Constants 👑

• NVME_FEAT_NS_NO_WRITE_PROTECT — No Write Protect. The namespace is free, unbothered, main character energy, write whatever you want to it. 💖
• NVME_FEAT_NS_WRITE_PROTECT — Write Protect. The namespace is locked down, no writes happening. Lowkey iconic of it honestly.
• NVME_FEAT_NS_WRITE_PROTECT_PWR_CYCLE — Write Protect Until Power Cycle. Protected for now, but the second the power cycles it's back to being writable. She's dramatic but temporary. 🦋
• NVME_FEAT_NS_WRITE_PROTECT_PERMANENT — Permanent Write Protect. No take-backs. That namespace is protected forever, periodt. 💀

---

Heads up babes: NVME_FEAT_NS_WRITE_PROTECT_PERMANENT does exactly what it says. Permanent means permanent. Choose your destiny wisely. 🌈

---

That's the whole page, bestie — you ate it. 💅

This little page lives in the libnvme API manual, and it was dated July 2026. Bye pookie, go protect a namespace responsibly! 🎀✨🫶