nvme_init_auth_send(9)

💅 nvme_init_auth_send(9) — the libnvme API manual, but make it cute

okay bestie, welcome to the nvme_init_auth_send(9) page — yes that's the section 9, we're in kernel/API land now, put your hair up 🎀 this one's from the libnvme API manual and it's literally about prepping a passthru command so you can send auth stuff. iconic behaviour honestly.

✨ NAME ✨

nvme_init_auth_send — initialize the passthru command for the Authentication Send command 🫶

🌸 SYNOPSIS 🌸

void nvme_init_auth_send (struct libnvme_passthru_cmd *cmd , __u16 spsp
, __u8 secp , __u32 tl , void *data , __u32 len );

🦋 ARGUMENTS 🦋

• cmd — the passthru command you're gonna use, like, this is the thing getting filled in 💖
• spsp — the Security Protocol Specific field, that's your __u16 bestie
• secp — the Security Protocol, a lil __u8 guy
• tl — the protocol specific transfer length (__u32, no cap)
• data — the authentication message payload buffer you're sending out 📨
• len — the data length of that payload, in bytes, fr fr

💜 DESCRIPTION 💜

so what this does is it initializes the passthru command buffer for the Fabrics Authentication Send command ✨ which is the one you use to send a KX-HMAC-CHAP authentication message (like, for example, struct nvmf_auth_kxchap_reply) to a controller. yes, to a controller. main character energy 👑

and the vibe check on this one: it's an NVMe-over-Fabrics specific command — like, it's not out here doing its own thing, it reuses the SECP/SPSP0/SPSP1/TL field encoding of the Security Send command 🌈 so if you know Security Send, you already kinda know this. iykyk 💅

lowkey important: it's void, so don't go looking for a return value, she gives you nothing back except a nicely initialized cmd. periodt.

and that's the whole page, bestie — no skipped bits, no crumbs left behind 🍓

sign-off szn 🎀 this was nvme_init_auth_send(9) from the libnvme API manual, dated October 2026 — mwah, go slay your auth messages 💖✨