nfs3svc_encode_entryplus3(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ nfs3svc_encode_entryplus3 ✨

okay so bestie, welcome to another episode of the Kernel API Manual πŸ’… and today's main character is a little function called nfs3svc_encode_entryplus3 β€” it's the one that encodes one NFSv3 READDIRPLUS entry. that's it, that's the vibe. πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

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

like, yes, it's a whole mouthful, but we move πŸ’–


🌸 ARGUMENTS 🌸

  • data β€” the directory context. it's giving "the whole situation" energy πŸ—‚οΈ
  • name β€” the name of the object we're encoding. the moment. the icon. ✨
  • namlen β€” how long that name is, in bytes. we're counting, bestie πŸ“
  • offset β€” the offset of the previous entry. yes, previous. pay attention 🫢
  • ino β€” the fileid of this entry. its literal ID, no cap πŸ”₯
  • d_type β€” unused. bestie's just here for moral support, she does nothing πŸ’€

πŸ‘‘ DESCRIPTION πŸ‘‘

so here's the tea β˜• β€” this function returns:

  • 0 β€” slay! the entry was successfully encoded πŸŽ‰
  • -EINVAL β€” uh oh, an encoding problem happened 😭 and the secondary status code lives in resp->common.err, so go look there

on exit, these fields get updated, periodt:

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

like three little glow-ups on the way out πŸŒˆπŸ’…


🧚 SEE ALSO 🧚

go read them, iykyk πŸ“šβœ¨


and that's the whole page, bestie 🫢 shoutout to the source ./fs/nfsd and the date October 2026 β€” catch you on the next manpage, mwah πŸ’œπŸŽ€

πŸ“¦ where this page comes from