libnvmf_tid_set_identity(9)

📦 version 3.2, in arch rolling

💅 libnvmf_tid_set_identity(9) — the libnvme API manual, bestie edition

okay so you're looking at libnvmf_tid_set_identity, straight out of the libnvme API manual (yes, the whole page is literally named after it, slay). this is the one that sets your subsystem and host identity together, in one little call, no cap 🎀

✨ NAME ✨

libnvmf_tid_set_identity — set the subsystem and host identity together. both of them. at once. iconic behavior honestly 🫶

🌸 SYNOPSIS 🌸

int libnvmf_tid_set_identity (struct libnvmf_tid *tid , const char
*subsysnqn , const char *hostnqn , const char *hostid );

that's it, that's the whole vibe ✨

🦋 ARGUMENTS 🦋

  • tid — the transport ID. the main character of this function, honestly.
  • subsysnqn — the subsystem NQN, or NULL to leave it unchanged.
  • hostnqn — the host NQN, or NULL to leave it unchanged.
  • hostid — the Host Identifier, or NULL to leave it unchanged (or derive it).

pass NULL, leave the field alone. simple as that 💅

💜 DESCRIPTION 💜

so listen, identity gets applied after addressing — which subsystem you're talking to, and which host persona you're showing up as, are both decided by context. and when you pass a NULL argument, that field just stays exactly as-is. that's literally why these three get set through one single call instead of per-field setters. (addressing doesn't even have setters — it's construction-only, periodt.)

now, hostid is never left to chance, and I mean never 🔥 when no hostid is set but the resulting hostnqn carries a UUID (nqn.2014-08.org.nvmexpress:uuid:<X>), the hostid gets derived from it — and it's the deterministic, per-host value (TP4126), never a random one. no vibes-based randomness here, bestie.

⚠️ and a hostid without a hostnqn? rejected. flat out. one host is one (hostnqn, hostid) pair — that's the rule, iykyk 💀

🌈 RETURN 🌈

  • 0 on success (we love a win) 🎉
  • -EINVAL for a NULL tid or a hostid without a hostnqn
  • -ENOMEM on allocation failure 😭

and that's the page, bestie!! this gem comes to you courtesy of the libnvme API manual, dated October 2026 — mwah, go set some identities 💖✨🎀🦋

📦 where this page comes from