libnvme(2)

✨ NAME ✨

enum nvme_ns_write_protect_cfg — bestie, it's the Write Protection - Write Protection State. yes the name really does say write protection twice. she contains multitudes. 💅

---

🎀 SYNOPSIS 🎀

okay so here's the whole enum, look at her:

enum nvme_ns_write_protect_cfg {
    NVME_NS_WP_CFG_NONE ,
    NVME_NS_WP_CFG_PROTECT ,
    NVME_NS_WP_CFG_PROTECT_POWER_CYCLE ,
    NVME_NS_WP_CFG_PROTECT_PERMANENT

};

four little constants, four whole vibes. let's get into it 🦋

---

🌸 Constants 🌸

• NVME_NS_WP_CFG_NONE — No Write Protect. the namespace is free, nothing's locked, she's living her life, zero restrictions. the wild west fr fr 💖
• NVME_NS_WP_CFG_PROTECT — Write Protect. it's protected. that's it, that's the whole constant, she said what she said 🌈
• NVME_NS_WP_CFG_PROTECT_POWER_CYCLE — Write Protect Until Power Cycle. locked down for now, but the second the power cycles she's back. temporary main character energy ⭐
• NVME_NS_WP_CFG_PROTECT_PERMANENT — Permanent Write Protect. the forever lock. no take-backs, no power cycle escape hatch, she's staying protected periodt. 💀 handle with care bestie, the name is not playing 😭

not me noticing the only difference between NVME_NS_WP_CFG_PROTECT_POWER_CYCLE and NVME_NS_WP_CFG_PROTECT_PERMANENT is whether the power cycle saves you. that's the whole plot twist 🫶

---

and that's the page, my love ✨ that was enum nvme_ns_write_protect_cfg from the libnvme(2) API Manual, dated July 2026. go forth and protect your namespaces responsibly, ily, bye 👑💜