nvme_mi_admin_sanitize_nvm(2)

✨ nvme_mi_admin_sanitize_nvm(2) ✨

okay bestie, sit down, hydrate, and let me tell you about a little function from the libnvme API manual that literally nukes data. yes. for real. 💅

---

🌸 NAME 🌸

nvme_mi_admin_sanitize_nvm — start a subsystem Sanitize operation

like, it kicks off the whole sanitize thing. that's the vibe. 🧚

---

🦋 SYNOPSIS 🦋

int nvme_mi_admin_sanitize_nvm (nvme_mi_ctrl_t ctrl , struct
nvme_sanitize_nvm_args *args );

yes it's giving "two arguments and a dream". let's meet them. 👑

---

🎀 ARGUMENTS 🎀

• ctrl — the Controller you're sending the command to. your main character. 🌟
• args — the Sanitize command arguments. all the deets, all the feels. 💖

---

🌈 DESCRIPTION 🌈

so, a sanitize operation alters all user data in the NVM subsystem such that recovery of any previous user data from any cache, the non-volatile media, or any Controller Memory Buffer is not possible. not. possible. bestie. it's gone gone. 💀

The Sanitize command starts a sanitize operation or to recover from a previously failed sanitize operation. The sanitize operation types that may be supported are Block Erase, Crypto Erase, and Overwrite. 🍓

and here's the part you absolutely cannot skip: all sanitize operations are processed in the background, i.e., completion of the sanitize command does not indicate completion of the sanitize operation. so when the call comes back, do NOT assume the data is gone. it's still cooking. 🙈

---

⭐ RETURN ⭐

it gives you the nvme command status if a response was received (see enum nvme_status_field) — or -1 with errno set otherwise. iykyk. 😭

---

and that's the whole page, no cap. this one came straight out of the libnvme API manual, dated July 2026 — periodt. go forth and sanitize responsibly, bestie 🫶✨