nfsd_symlink(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay so bestie, welcome to nfsd_symlink(9) β€” it’s giving Kernel API Manual energy ✨ and the vibe is literally β€œCreate a symlink and look up its inode.” No cap.

✨ SYNOPSIS ✨

__be32 nfsd_symlink (struct svc_rqst *rqstp , struct svc_fh *fhp , char *fname , int flen , char *path , struct nfsd_attrs *attrs , struct svc_fh *resfhp );

πŸŽ€ ARGUMENTS πŸŽ€

  • rqstp β€” the RPC transaction that’s being executed 🫢
  • fhp β€” the NFS filehandle of the parent directory
  • fname β€” the filename of the new symlink
  • flen β€” the length of fname
  • path β€” the content of the new symlink (NUL-terminated) 🌸
  • attrs β€” the requested attributes of the new object
  • resfhp β€” the NFS filehandle of the new object

πŸ¦‹ DESCRIPTION πŸ¦‹

N.B. After this call _both_ fhp and resfhp need an fh_put. Both bestie. Not one. Both. This is important πŸ’…

Returns nfs_ok on success, or an nfsstat in network byte order.

🌈 SEE ALSO 🌈

Kernel file ./fs/nfsd/vfs.c and the whole friend group:


xoxo, your kernel bestie 🫢 this page is from ./fs/nfsd, dated October 2026, and it’s the nfsd_symlink(9) manual page. Slay. πŸ’…βœ¨

πŸ“¦ where this page comes from