nvme_tls_psk_refresh(9)

🦋 Refresh TLS PSK — the nvme_tls_psk_refresh glow-up 🦋

Okay bestie, welcome to nvme_tls_psk_refresh(9) from the Kernel API Manual. This page is literally about refreshing a TLS PSK, and it's lowkey iconic. 💅

✨ NAME ✨

nvme_tls_psk_refresh — Refresh TLS PSK. That's the whole name, no cap. 🎀

🌸 SYNOPSIS 🌸

struct key * nvme_tls_psk_refresh (struct key *keyring , const char
       *hostnqn , const char *subnqn , u8 hmac_id , u8 *data , size_t data_len
       , const char *digest );

💖 ARGUMENTS 💖

• keyring — the keyring that's holding the TLS PSK. Like, that's where the key lives, bestie. 🔑
• hostnqn — the Host NQN to use. 🖥️
• subnqn — the Subsystem NQN to use. 🧚
• hmac_id — the hash function identifier. Give it the ID, it does the hash vibe check. 🌈
• data — the TLS PSK key material. The actual key stuff. 🍓
• data_len — the length of data. Gotta know how much key material we're working with. 📏
• digest — the TLS PSK digest. Yes, it's digesting. 💫

🔥 DESCRIPTION 🔥

So here's the tea: this function refreshes a generated version 1 TLS PSK with the identity generated from hmac_id, hostnqn, subnqn, and digest, inside the keyring given by keyring. It's giving “update the key, but make it secure.” 👑

It returns the updated key on success, or an error pointer otherwise. So it can hand you back an error pointer, fr fr. 😭

👑 SEE ALSO 👑

Kernel file ./drivers/nvme/common/keyring.c — go look, iykyk. 📂

Signing off from ./drivers/nvme/common on October 2026, with page nvme_tls_psk_refresh(9) — xoxo, your kernel bestie 💖🫶