libnvmf_exclusion_write(9)

💖 NAME 💖

libnvmf_exclusion_write — atomically replace a list's contents. This is the libnvme API manual page for libnvmf_exclusion_write(9), and honestly? It’s giving “whole-list glow-up, but make it atomic.” 🦋✨

✨ SYNOPSIS ✨

int libnvmf_exclusion_write (struct libnvme_global_ctx *ctx , const char
       *name , const char *text , uint64_t version );

🎀 ARGUMENTS 🎀

• ctx — the libnvme global context; it must not be NULL. Like, do not pass NULL, bestie. 🙈
• name — list name. Simple, iconic, to the point. 💅
• text — the full replacement contents. Every "exclusion = ..." line is validated and must sit inside the [exclusions] section; invalid entries cause -EINVAL and no write. So invalid stuff does not get written — periodt. 🛑
• version — the token from a prior libnvmf_exclusion_read. The write proceeds only if the on-disk list still matches version; otherwise it returns -ESTALE and leaves the file untouched, so a concurrent editor's changes are never silently overwritten. This is the “don’t let someone else’s edits get ghosted” check. 👻

🌸 DESCRIPTION 🌸

The replacement is installed atomically (temp file + rename) with mode 0644. That’s the whole vibe: temp file, rename, mode 0644, all in one neat little package. 🎁

💜 RETURN 💜

• 0 — success, slay. ✅
• -ESTALE — the list changed since version was read. 😭
• -EINVAL — an invalid entry or name. 🙅
• negative errno — otherwise. 💀

Okay that’s the whole page, bestie. 🫶 This gem is dated October 2026, sourced under libnvmf_exclusion_write, and the footer name/version situation is libnvmf_exclusion_write(9). Mwah. 💋🎀