nfs_fattr_ma...d_free_names(9)

💅 nfs_fattr_map_and_free_names(9) — from the Kernel API Manual, bestie

okay so picture this: you're deep in the kernel, you've got NFSv4 owner/group strings just sitting there in your nfs_fattr, and you need them as real live numbers. that's the whole gig. this is the helper that does the glow-up and then cleans up after itself. iconic behavior honestly 🧚

---

✨ NAME ✨

nfs_fattr_map_and_free_names — maps the owner/group strings into uid/gid and then frees them. like, does the conversion AND takes out the trash. main character energy fr fr 💅

---

🌸 SYNOPSIS 🌸

void nfs_fattr_map_and_free_names (struct nfs_server *server , struct nfs_fattr *fattr );

---

🎀 ARGUMENTS 🎀

• server — pointer to the filesystem nfs_server structure. yes bestie, the actual server struct, the whole vibe check of which filesystem we're on 🦋
• fattr — a fully initialised nfs_fattr structure. like, fully. don't come at it half-set-up, that's not the move 🙈

---

🔥 DESCRIPTION 🔥

so here's what this lil helper does, and honestly it's giving efficiency 👑

it takes the cached NFSv4 owner/group strings hanging out in fattr, maps them into their numeric uid/gid equivalents, and then — the way that it just frees the cached strings afterwards — periodt. conversion done, memory released, no leftovers, no crumbs. we love a clean exit ✨

lowkey the order matters conceptually: map first, free second. it's mapping the cached strings, then freeing those strings. that's the whole sentence, don't overthink it 🫶

---

🌈 SEE ALSO 🌈

kernel file ./fs/nfs/nfs4idmap.c, plus these two besties who are definitely in the group chat:

• nfs_fattr_init_names(9)
• nfs_fattr_free_names(9)

---

and that's the page!! 💖 source/version: ./fs/nfs, dated October 2026 — go forth, map those names, free those strings, slay 💅🎀⭐