nvme_scan_tls_keys(2)

✨ nvme_scan_tls_keys ✨

okay bestie, gather round, because we're looking at a little function from the libnvme API manual and it's genuinely so cute once you get it. it's called nvme_scan_tls_keys and no, it does not scan you for red flags (that's a different syscall, and it doesn't exist yet, unfortunately 😭). it scans a keyring. for TLS keys. one by one. periodt. 💅

---

🌸 NAME 🌸

nvme_scan_tls_keys — iterate over TLS keys in a keyring

like, it walks through your keyring and visits every TLS key in there, one at a time, like it's doing a little tour 👑✨

---

🎀 SYNOPSIS 🎀

int nvme_scan_tls_keys (const char *keyring , nvme_scan_tls_keys_cb_t cb
, void *data );

---

💖 ARGUMENTS 💖

• keyring — the keyring that's holding the TLS keys. this is the place we're scanning, the venue of the whole event 🎉
• cb — the callback function. this is your girl — the function that gets called for every key that makes it through the vibe check.
• data — a pointer to the data you want passed along to cb. it just rides along for the journey and shows up in cb's hands 🫶

---

🦋 DESCRIPTION 🦋

so what actually happens: it iterates over keyring and calls cb for each TLS key it finds. that's the whole plot. no cap.

when keyring is NULL, the default .nvme keyring is used instead — so if you're feeling lazy you can just pass NULL and let the default .nvme keyring carry the whole thing, main character energy honestly 🌈

but here's the part where the standards get strict: a TLS key must be of type psk, and its description must be of the form:

NVMe<0|1><R|G>0<1|2> <identity>

if it's not type psk, or the description isn't that exact shape, it gets skipped during iteration. like, not invited. not on the list. left on read 🙈💀 it's not an error though — it just doesn't get visited.

---

⭐ RETURN ⭐

• the number of keys for which cb was called — i.e. how many keys actually made it through and got their callback moment 👏
• or -1 with errno set, when something goes wrong 😭

---

ngl if you get -1, please check errno before you spiral. it's giving "the info is literally right there".

---

sign-off time, my love 🧚💜 this lil page came from the libnvme API manual, dated July 2026, and it's filed under nvme_scan_tls_keys with the section nvme_scan_tls_keys(2). slay, go scan some keys, and hydrate bestie 🍓✨