nfssvc_encode_entry(9)

💖 nfssvc_encode_entry 💖

okay so bestie, welcome to the Kernel API Manual ✨ — this one is a lil function called nfssvc_encode_entry, and it does exactly one (1) thing: it encodes one NFSv2 READDIR entry. that's it. that's the whole vibe 🎀

---

✨ SYNOPSIS ✨

int nfssvc_encode_entry (void *data , const char *name , int namlen ,
       loff_t offset , u64 ino , unsigned int d_type );

---

🦋 ARGUMENTS 🦋

• data — the directory context 🗂️ like, the whole scene this entry lives in.
• name — the name of the object you're encoding. the star of the show 👑
• namlen — how long that name is, counted in bytes (bytes!! not vibes).
• offset — the offset of the previous entry. yes, previous. not this one. don't ask me why, that's just the lore 🫶
• ino — the fileid of this entry. its little ID card 💅
• d_type — unused. literally unused. it's giving decorative. it's there, it's cute, it does nothing 🌸

---

💜 DESCRIPTION 💜

so here's the tea ☕ — this function encodes one NFSv2 READDIR entry, and then it tells you how it went with these return values:

• 0 — slay 💅 the entry was successfully encoded.
• -EINVAL — uh oh 😭 an encoding problem occurred. the secondary status code lives in resp->common.err (iykyk).

and when it's done, on exit, these fields get updated:

• resp->xdr
• resp->common.err
• resp->cookie_offset

that's the full list, no cap. three fields. updated. periodt 🎀

ngl bestie, keep an eye on that -EINVAL path — if the encode goes sideways, resp->common.err is where the real story is 🔥

---

🌈 SEE ALSO 🌈

• Kernel file ./fs/nfsd/nfsxdr.c
• svcxdr_encode_stat(9)
• svcxdr_decode_fhandle(9)
• svcxdr_encode_fattr(9)
• nfssvc_encode_nfscookie(9)

go read those too, they're all in the same friend group fr fr 🫶✨

---

aaaand that's the page!! 💖 this whole thing lives in ./fs/nfsd and it's dated October 2026 — so go forth, encode that entry, and remember: one entry at a time, bestie 🧚 💜