nfs_setattr_update_inode(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… nfs_setattr_update_inode(9) πŸ’…

okay so this is a page from the Kernel API Manual bestie, section 9, and the star of the show is nfs_setattr_update_inode β€” the little function whose whole personality is "the setattr call happened, now let's make the inode metadata match". ✨


πŸ¦‹ NAME πŸ¦‹

nfs_setattr_update_inode β€” update inode metadata after a setattr call. that's it, that's the vibe. πŸŽ€


🌸 SYNOPSIS 🌸

void nfs_setattr_update_inode (struct inode *inode , struct iattr *attr
, struct nfs_fattr *fattr );

she returns void (no little gift back, just vibes) and takes three pointers. slay. πŸ’…


✨ ARGUMENTS ✨

  • inode β€” pointer to struct inode. the main character of this whole operation, honestly. πŸ‘‘
  • attr β€” pointer to struct iattr. the attributes we're working with. πŸŽ€
  • fattr β€” pointer to struct nfs_fattr. the NFS-flavoured attribute buddy. πŸ¦‹

πŸ’€ NOTE πŸ’€

so here's the tea: we do this in the *proc.c in order to ensure that it works for things like exclusive creates too. like, that's the whole reason. no cap. πŸ”₯

genuinely do keep that in mind β€” the placement in *proc.c isn't random, it's the thing making exclusive creates behave. πŸ™ˆ

🫢 SEE ALSO 🫢

the whole friend group, in order (yes, all of them, i'm not skipping anyone 😭):

go read them, i believe in you πŸ’–


and that's the page!! sign-off time 🧚: it lives at ./fs/nfs, the date on it is October 2026, and the whole thing is filed under nfs_setattr_update_inode(9) in the Kernel API Manual. bye bestie, go update some inodes πŸ’œβ­πŸ“

πŸ“¦ where this page comes from