namespace_update_uuid(9)

💅 namespace_update_uuid(9) — like, the Kernel API Manual, bestie ✨

Okay so real talk, this is a page from the Kernel API Manual and it's all about namespace_update_uuid — the function that checks whether a uuid is actually unique and whether we're lowkey "renaming" something. Yes, "renaming" in quotes, the kernel is being mysterious about it, we love that for us 🎀

---

🌸 NAME 🌸

namespace_update_uuid — check for a unique uuid and whether we're "renaming" 💫

---

✨ SYNOPSIS ✨

int namespace_update_uuid (struct nd_region *nd_region , struct device
*dev , uuid_t *new_uuid , uuid_t **old_uuid );

That's the whole vibe check right there, no cap 🔥

---

🦋 ARGUMENTS 🦋

• nd_region — the parent region, so we can update all the dimms in the set 🫶 like it's the mother of the group chat and everyone's getting the news
• dev — namespace type, and it's there for generating the label_id 👑
• new_uuid — the incoming uuid, the fresh one, the new main character 🌈
• old_uuid — a reference to the uuid storage location in the namespace object 📍 it's giving "keep the receipts" iykyk

---

💀 RETURN 💀

0 on success, or -errno on error 😭 periodt.

---

🧚 SEE ALSO 🧚

Kernel file ./drivers/nvdimm/namespace_devs.c — plus these iconic little references, go read them fr fr:

• nd_is_uuid_unique(9)
• shrink_dpa_allocation(9)
• space_valid(9)
• grow_dpa_allocation(9)
• create_namespace_pmem(9)

---

💖 obligatory note bestie: the return is literally "0 on success on -errno on error" — so yes, success is 0 and errors come back as -errno. Keep that energy.

---

That's the whole thinggg ✨ This little love letter lives in ./drivers/nvdimm, it's from October 2026, and it ships as part of the Kernel API Manual — namespace_update_uuid(9), slay 💅🎀