libnvmf_uri_parse(9)

🌸 libnvmf_uri_parse(9) — like, the whole vibe 💅

okay bestie, welcome to libnvmf_uri_parse, straight outta the libnvme API manual ✨ this is a section 9 page (kernel/API land, iykyk) and it's literally just one little function that eats a URI string and hands u back a shiny object 🎀

---

✨ NAME ✨

libnvmf_uri_parse — parse the URI string 🦋 that's it. that's the whole job. no cap.

---

✨ SYNOPSIS ✨

int libnvmf_uri_parse (const char *str , struct libnvmf_uri **uri );

like yes the spacing is a lil weird, do NOT come for me, that's exactly how it's written 💀 copy it verbatim bestie 🫶

---

✨ ARGUMENTS ✨

• str — the URI string itself 🌈 the raw text u want parsed, ur main character input fr
• uri — the URI object to return 👑 this is the out-param, so it's a struct libnvmf_uri ** — a pointer to a pointer, yes it's giving double-pointer energy and yes that's correct 💅

---

✨ DESCRIPTION ✨

so here's the tea ☕ — libnvmf_uri_parse parses the URI string as defined in the NVM Express Boot Specification 🌟 that's the actual spec it follows, not vibes-based parsing, an actual spec, iconic behavior honestly 🎀

the supported URI elements lowkey look exactly like this 👇

nvme+tcp://userhost:port/subsys_nqn/nid?query=val#fragment

look at her. the whole structure is right there in one line 🌸 u got the scheme nvme+tcp://, then userhost:port, then /subsys_nqn/nid, then the ?query=val bit, then #fragment at the end — all the pieces, in order, slaying ✨

---

✨ RETURN ✨

• 0 on success 😌💖 everything worked, go off
• negative error code otherwise 😭💀 so like, if it's negative, something went sideways — check it, don't ignore it, that's the whole point of a return value bestie

---

ngl if u skip the return check ur gonna have a bad time 🙈 0 = good, negative = bad. that's the vibe check. don't fail it.

---

okay that's the page!! this was libnvmf_uri_parse(9) from the libnvme API manual, dated October 2026 — go parse some URIs, ily, bye 🧚💜🍓