libnvmf_exclusion_create(9)

📦 version 3.2, in arch rolling

💅 libnvmf_exclusion_create — from the libnvme API manual ✨

okay so bestie, quick vibe check: we're in section 9, this is the libnvmf_exclusion_create page from the libnvme API manual, and it's literally about spinning up a brand-new exclusion list. that's it, that's the whole main character energy of this page 🎀

🌸 NAME 🌸

libnvmf_exclusion_create — create a new exclusion list. periodt. 💅

✨ SYNOPSIS ✨

int libnvmf_exclusion_create (struct libnvme_global_ctx *ctx , const
char *name );

like, that's the whole signature, no cap. 🫶

🦋 ARGUMENTS 🦋

  • ctx — the libnvme global context. it must not be NULL, fr fr, do not pass a null bestie, that's not the move 🙈
  • name — the name of your list, and here's the tea: it gets used as the actual filename, shaped like <dir>/<name>.conf. so like, your name choice is lowkey iconic AND functional 💖

🌈 RETURN 🌈

so what comes back?

  • 0 on success — we ate, we slayed, list created 👑
  • -EEXIST if the list already exists — she's already there, babe, no duplicates 💀
  • a negative errno otherwise — anything else goes wrong, you get a negative errno back, and that's your sign to go check what happened 🔥
ngl, always check the return value. 0 means you're golden; -EEXIST means she already exists so maybe don't fight it. negative errno = something else is up and it's giving "go read the errno docs" energy 😭

so yeah, that's the whole page, bestie — short, sweet, and fully slaying 💜

sign-off szn: this lil page came from the libnvme API manual, dated October 2026, and the header/footer were out here calling her libnvmf_exclusion_create(9) the entire time. mwah, take care of her 🧚‍♀️🌸

📦 where this page comes from