LIBNVMF_REGISTRY_DEVICE_FOR_EACH-LIBNVME3(2)

✨ NAME ✨

libnvmf_registry_device_for_each — bestie, this is the one that iterates over live controller registry entries 💅 like it literally walks the registry and hands you every entry that's still alive and thriving.

---

🌸 SYNOPSIS 🌸

int libnvmf_registry_device_for_each (struct libnvme_global_ctx *ctx ,
int (*callback)(const char *device, void *user_data) , void *user_data
);

okay so that's the whole vibe right there — one call, one callback, zero drama (mostly) 🫶

---

🎀 ARGUMENTS 🎀

• ctx — your libnvme global context ✨ heads up though: this one must not be NULL, like fr fr, don't even try it 🙈
• callback — the callback that gets invoked for each live entry 💖 every single one, bestie
• user_data — your own lil payload, passed straight through to callback 🍓 it's yours, do what you want with it

---

🦋 DESCRIPTION 🦋

So what actually happens? It scans the registry directory and invokes callback for each entry whose corresponding /dev/nvmeN device node exists 👑

Stale entries left behind after a controller is removed? Silently skipped. Not a word. Not a peep. They just get ghosted 💀✨

⚠️ Now here's the important bit, bestie, don't scroll past this: the existence check is advisory. A device may be removed between the check and the callback invocation — like the check says "she's here!" and then she's literally gone 😭 so callers should handle ENOENT gracefully. No cap, this is a real one.

---

🔥 RETURN 🔥

• 0 on success — slay 💅
• negative errno if the registry directory cannot be opened 😔
• 0 when the directory does not exist — which just means nothing is registered, so like, nothing to see here, everything's fine 🌈

---

and that's the whole page, bestie, you ate it up 👑

🌸 mwah 💋 this gem came to you from the libnvme API manual, section 9, dated October 2026 — iconic, periodt 🎀