nfsd_create_setattr(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

nfsd_create_setattr β€” setting a freshly created file's attributes, okurrr ✨ (this is the Kernel API Manual, bestie, and yes we're reading kernel docs for fun now πŸŽ€)


🌸 SYNOPSIS 🌸

__be32 nfsd_create_setattr (struct svc_rqst *rqstp , struct svc_fh *fhp
, struct svc_fh *resfhp , struct nfsd_attrs *attrs );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • rqstp β€” the RPC transaction that's being executed rn, like the group chat message currently being sent πŸ’Œ
  • fhp β€” the NFS filehandle of the parent directory (the one that's giving birth to the new object, lowkey iconic of it πŸ‘‘)
  • resfhp β€” the NFS filehandle of the new object, the main character we just made ✨
  • attrs β€” the attributes that got requested for the new object, aka the vibe the file is supposed to have 🌈

πŸ’– DESCRIPTION πŸ’–

So here's the whole tea, bestie: this thing returns nfs_ok when it works πŸŽ‰, or an nfsstat in network byte order when it doesn't 😭. That's it, that's the description β€” no cap, she's short but she's honest.

Ngl, "an nfsstat in network byte order" is the important bit β€” it's not a plain int sitting there looking cute, it's byte-swapped, so don't go comparing it raw fr fr πŸ’€

⭐ SEE ALSO ⭐

Kernel file ./fs/nfsd/vfs.c, plus the whole friend group that comes with it 🫢:


And that's the page, bestie πŸ’…βœ¨ this one lives in ./fs/nfsd, it's dated October 2026, and it goes by nfsd_create_setattr(9) β€” memorize the glow-up, it's giving legend behavior πŸŽ€πŸ’œπŸ¦‹

πŸ“¦ where this page comes from