nvmf_get_discovery_log(2)

💖 nvmf_get_discovery_log — bestie edition 💖

okay so this is a page from the libnvme API manual (that's the (2) vibe, iykyk) and it's all about one lil function called nvmf_get_discovery_log. buckle up 🎀

---

✨ NAME ✨

nvmf_get_discovery_log — returns the discovery log page, periodt.

---

🌸 SYNOPSIS 🌸

int nvmf_get_discovery_log (nvme_ctrl_t c , struct nvmf_discovery_log
**logp , int max_retries );

like… it takes three things and gives you back an int. slay.

---

🦋 ARGUMENTS 🦋

• c — the discovery controller you're using, bestie. that's your entry point 💅
• logp — a pointer to the log page that's gonna get handed back to you 🌈
• max_retries — how many times you wanna retry if things go sideways 😭

---

👑 DESCRIPTION 👑

so here's the tea: the memory that gets allocated for the log page — the stuff that comes back to you in logp — must be freed by the caller using free. yep, that's on YOU. no one else is coming to clean that up, so don't ghost it 🙈

---

💀 NOTE 💀

ngl, consider using nvmf_get_discovery_wargs instead. just saying. the way that this one is lowkey the older option… 🫶

---

🌟 RETURN 🌟

• 0 on success — we love a win ✨
• on failure, -1 is returned and errno is set 💀

fr fr, always check that return value. the errno is giving you the actual reason and it's not gonna say it twice.

---

and that's the whole page, babe 🧚💜 this one came from the libnvme API manual, dated July 2026, and it's filed under nvmf_get_discovery_log in section (2) — mwah, go free your memory bestie 💖