libnvme(2)

💖 libnvme(2) — bestie's guide to enum nvme_id_ctrl_nwpc 💖

okay so listen. this is a page from the API Manual for libnvme, and we're about to get into namespace write protection. it's giving very much "who's allowed to lock things and how hard can they lock them" energy. stay with me, it's literally not that deep once you see it. 🎀

---

✨ NAME ✨

enum nvme_id_ctrl_nwpc — this field tells you which optional namespace write protection capabilities your controller supports. (optional! read the fine print bestie 🔍)

---

🌸 SYNOPSIS 🌸

enum nvme_id_ctrl_nwpc {
    NVME_CTRL_NWPC_WRITE_PROTECT ,
    NVME_CTRL_NWPC_WRITE_PROTECT_POWER_CYCLE ,
    NVME_CTRL_NWPC_WRITE_PROTECT_PERMANENT

};

---

👑 Constants 👑

okay so there's three of them and they're each a little bit more intense than the last. keep up. 💅

• NVME_CTRL_NWPC_WRITE_PROTECT — if this bit is set, then the controller shall support the No Write Protect and Write Protect namespace write protection states, and it may support the Write Protect Until Power Cycle state and the Permanent Write Protect namespace write protection states. so like, the first two are a promise, the other two are a maybe. 🫶
• NVME_CTRL_NWPC_WRITE_PROTECT_POWER_CYCLE — if this bit is set, then the controller supports the Write Protect Until Power Cycle state. so it stays protected until you yank the power. classic power-cycle reset, the og "turn it off and on again". 🔥
• NVME_CTRL_NWPC_WRITE_PROTECT_PERMANENT — if this bit is set, then the controller supports the Permanent Write Protect state. permanent. like, permanent permanent. no take-backs, no power cycle, no nothing. be so for real before you touch this one. 😭💀

fr fr: "shall" and "may" are doing heavy lifting here. one is a guarantee, the other is a vibe. read them again if you skimmed. 🙈

---

<div></div>

and that's the whole page, bestie!! enum nvme_id_ctrl_nwpc came from the libnvme API Manual, this version's dated July 2026, and it lives right here under section libnvme(2) — see you in the next one, mwah 💋💖 ✨🦋🌸