libnvme(9)

💖 NAME 💖

struct nvme_security_send_args — bestie, these are the arguments for the NVMe Security Send command ✨

This lil cutie lives in the libnvme(9) API manual, and we're gonna go through every single field together, no skipping, fr fr 🫶

---

🌸 SYNOPSIS 🌸

struct nvme_security_send_args {
    __u32 *result;
    void *data;
    int args_size;
    int fd;
    __u32 timeout;
    __u32 nsid;
    __u32 tl;
    __u32 data_len;
    __u8 nssf;
    __u8 spsp0;
    __u8 spsp1;
    __u8 secp;
 };

Okay look at her. Twelve fields. Every one of them matters. Let's go 💅

---

🎀 Members 🎀

• result — the command completion result, straight outta CQE dword0. the receipts, literally 📬
• data — the security data payload you're sending out into the world. go lil payload go 🦋
• args_size — the size of struct nvme_security_send_args itself. she's measuring herself, iconic 👑
• fd — the file descriptor of the nvme device. your golden ticket to the device 🎟️
• timeout — timeout in ms. don't be late bestie ⏰
• nsid — the namespace ID to issue the security command on. which namespace we vibing with today 🌈
• tl — protocol specific transfer length. very protocol. very specific. very transfer. very length. 💀
• data_len — data length of the payload, in bytes. count 'em 📏
• nssf — NVMe Security Specific field. the NVMe one specifically ✨
• spsp0 — Security Protocol Specific field. first half of the duo 🫶
• spsp1 — Security Protocol Specific field. second half of the duo, she completes the set 💖
• secp — Security Protocol. the protocol of security, periodt 🔥

---

no cap: every field above is listed exactly as the manual gives it, types and all. do not rename, do not merge, do not get cute with the struct. the struct stays the struct 💅

---

and that's the whole page, bestie!! 🌟

This one came from the struct nvme_security_send_args page in the libnvme(9) API Manual, dated August 2026 — so if you're reading this way in the future, hey, hi, hope the struct is still slaying 🧚💜