NVME_GET_LOG_CHANGED_ALLOC_NS_LIST(2)

💖 nvme_get_log_changed_alloc_ns_list — bestie's guide to the Changed Allocated Namespace List Log 💖

okay so real talk, this is one of those libnvme man pages (it lives in section 2 of the manual, the API-call girlies section 🎀), and it's genuinely so useful. Sit down, grab a strawberry drink 🍓, and let's get into it.

---

✨ NAME ✨

nvme_get_log_changed_alloc_ns_list — Retrieve Changed Allocated Namespace List Log

Like, the whole point of her: she goes and fetches you the log page that tells you which namespaces have had their allocated status change. That's it, that's the girl. 👑

---

🌈 SYNOPSIS 🌈

int nvme_get_log_changed_alloc_ns_list (int fd , bool rae , __u32 len ,
       struct nvme_ns_list *log );

no cap, that's the whole signature. four things go in, one int comes back out. 💅

---

🦋 ARGUMENTS 🦋

• fd — File descriptor of nvme device. literally the handle to the device you're talking to, nothing more, nothing less. 🔥
• rae — Retain asynchronous events. this is the bool that says "bestie, keep the async events, don't clear them". 👀
• len — The allocated length of the log page. as in, how much room you actually gave her to write into. respect the buffer, fr fr. 📏
• log — User address to store the log page. this is your memory, you're handing her the address, and she will fill it. struct nvme_ns_list *, exactly as promised. 🫶

---

💀 RETURN 💀

She gives you back the nvme command status if a response was received (peep enum nvme_status_field for what those statuses mean, iykyk), or -1 with errno set otherwise.

so if you get a -1, that's not a vibe, that's an error — go check errno, she always leaves a note. 😭

---

that's genuinely the whole page, bestie. no hidden options, no secret flags, just four args and a return value. short queen behavior honestly. ✨

---

okay and for the cute sign-off: this page comes from the libnvme API manual (that's the source, the version vibe) and it's dated July 2026. mwah, go forth and read your namespace lists. 💖🌟🎀