exportfs_encode_ino64_fid(9)

💅 exportfs_encode_ino64_fid(9) — the Kernel API Manual, bestie edition ✨

okay so real talk, this is a page from the Kernel API Manual and the function's whole name is exportfs_encode_ino64_fid(9) — yes it's a mouthful, yes it ate, we move. 🎀

---

🌸 NAME 🌸

exportfs_encode_ino64_fid — encode non-decodeable 64bit ino file id

like, it makes a file id that you literally cannot decode back. that's the whole vibe. it's giving one-way street energy 🦋

---

✨ SYNOPSIS ✨

int exportfs_encode_ino64_fid (struct inode *inode , struct fid *fid ,
       int *max_len );

that's the signature, copy it exactly, no cap. 💅

---

🫶 ARGUMENTS 🫶

• inode — the object to encode. this is the main character of the whole operation ngl 👑
• fid — where to store the file handle fragment. it's the lil spot where the goods go 🎀
• max_len — maximum length to store there (in 4 byte units). read that again, bestie: 4 byte units, not bytes. not me almost forgetting that 😭

---

💖 DESCRIPTION 💖

so this generic function is used to encode a non-decodeable file id for fanotify, and it's specifically for filesystems that do not support NFS export. 🔥

that's it, that's the whole job. it's a generic function, it does its one little thing iconically, and it does not care about your feelings about it. periodt. ⭐

heads up babe: "non-decodeable" is literally in the name — you're not getting that file id back. don't come crying to me. 🙈

---

🌈 SEE ALSO 🌈

• Kernel file ./fs/exportfs/expfs.c
• get_name(9)
• exportfs_encode_inode_fh(9)
• exportfs_encode_fh(9)

go read those too, iykyk 📚✨

---

🦋 ok that's the whole page, mwah 🫶 — this lil gem lives in ./fs/exportfs, it's dated October 2026, and it goes by exportfs_encode_ino64_fid(9). slay, bye bestie! 💜🌷