nfsd_link(9)

📦 version 7.3.1, in nixpkgs unstable

okay so bestie, welcome to nfsd_link, straight out of the Kernel API Manual (that's section 9 of the kernel manuals, iykyk) — it's the little guy that makes a link, and honestly it's kind of iconic.

🌸 SYNOPSIS 🌸

__be32 nfsd_link (struct svc_rqst *rqstp , struct svc_fh *ffhp , char
*name , int len , struct svc_fh *tfhp );

like, look at that signature. so much going on. slay. 💅

🦋 ARGUMENTS 🦋

  • rqstp — the RPC transaction context. your main character passport, basically.
  • ffhp — the file handle of the directory where the new link is gonna be created. this is the where.
  • name — the filename of the new link. this is the what.
  • len — the length of name, measured in octets. yes, octets. not vibes. octets. 🫶
  • tfhp — the file handle of an existing file object. this is the who's getting linked.

🎀 DESCRIPTION 🎀

okay so listen closely because this part is lowkey important: after this call _both_ ffhp and tfhp need an fh_put. BOTH. like not one, not the other, both. do not leave a file handle hanging, it's giving bad manners. 😭

and what does it give you back? a generic NFS status code in network byte-order ✨ (which is the fancy way of saying "big-endian, don't @ me").

fr fr, that fh_put on both handles is not a suggestion, bestie. it's the whole vibe check. 🔥

🌈 SEE ALSO 🌈

so there's a whole friend group here, and nfsd_link is not the only one in the group chat:

💀 not the full roster. twenty whole entries. they ate and left no crumbs.

nfsd_link(9) lives in ./fs/nfsd, it's dated October 2026, and it's from the Kernel API Manual — k that's the whole page, ily, go put your file handles back 🌸🦋💖

📦 where this page comes from