libnvme(2)

💖 libnvme(2) — the API manual, but make it make sense 💖

okay bestie, welcome to libnvme(2), the API manual 💅 today we're looking at one tiny lil enum and honestly? she's lowkey iconic. it's giving "three constants and a dream" ✨ let's get into it 🫶

---

✨ NAME ✨

enum nvme_lockdown_log_contents — the lockdown log page content attributes 🎀

like, it's the enum that tells you what kind of thing you're reading out of the lockdown log page. that's the whole vibe, no cap.

---

✨ SYNOPSIS ✨

enum nvme_lockdown_log_contents {
    NVME_LOCKDOWN_SUPPORTED_CMD ,
    NVME_LOCKDOWN_PROHIBITED_CMD ,
    NVME_LOCKDOWN_PROHIBITED_OUTOFBAND_CMD

};

look at her. three members, all up in there, exactly as written. don't touch, don't "fix" the spacing, she's perfect 🙈

---

✨ Constants ✨

these are the actual content values, kay? each one is a different flavored answer to "what's in this lockdown log entry":

• NVME_LOCKDOWN_SUPPORTED_CMD — Content value for Supported commands 💖 the "yep, you're allowed, go off queen" bucket.
• NVME_LOCKDOWN_PROHIBITED_CMD — Content value for prohibited commands 🚫 the "no bestie, absolutely not" bucket.
• NVME_LOCKDOWN_PROHIBITED_OUTOFBAND_CMD — Content value for prohibited side band commands 📵 the "no, and especially not from over there" bucket, i.e. commands blocked when they come in via side band. iykyk.

fr fr, those three descriptions are the entire story here. no hidden lore, no secret defaults, just three content values doing their little jobs 🌸

---

and that's the whole page, bestie. short, sweet, and absolutely ate 💅 this was pulled from the enum nvme_lockdown_log_contents API manual page, source/version libnvme(2), dated July 2026. periodt. 👑🌈⭐