libnvmf_traddr_is_numeric(9)

📦 version 3.2, in arch rolling

💅 libnvmf_traddr_is_numeric ✨

okay bestie, welcome to the libnvme API manual page for libnvmf_traddr_is_numeric(9) — she's a lil function with a big job and honestly? iconic. 🎀

🌸 NAME 🌸

libnvmf_traddr_is_numeric — literally just: would this address survive TID construction? 👀

🦋 SYNOPSIS 🦋

bool libnvmf_traddr_is_numeric (const char *traddr );

✨ ARGUMENTS ✨

  • traddr — a candidate traddr/host_traddr, or NULL. that's it, that's the whole vibe check 🫶

💖 DESCRIPTION 💖

so here's the tea, bestie: the TID constructors are picky. they accept a numeric IP only and they will straight-up reject a hostname. no cap. 💀

this function lets a caller check a candidate address — and decide whether it must resolve it first — before building the TID. and the slay part? it uses the exact same definition of "numeric" that the constructors use internally. same brain, same rules, fr fr. 🧠✨

and yes, that definition includes an IPv6 scope suffix, which counts as numeric. so don't come for her about that one, she knows. 💅

🔥 RETURN 🔥

  • true if traddr is a numeric address 🔥
  • false otherwise — and that includes when traddr is NULL, or when there's an allocation failure while checking 😭
ngl, that second false is the sneaky one — allocation failure also gives you false, so don't assume false always means "not numeric". 🙈

👑 SEE ALSO 👑

...okay there's genuinely nothing else listed here, so just go forth and build those TIDs, main character. 🌈

💜 that's the whole page, bestie — written through-and-through and not copy-pasted, promise. this gem comes to you from the libnvme API manual, dated October 2026, and the page header herself is libnvmf_traddr_is_numeric(9) — footer energy: October 2026 · libnvmf_traddr_is_numeric · libnvmf_traddr_is_numeric(9). mwah, bye 🍓💖

📦 where this page comes from