exportfs_encode_fh(9)

💅 exportfs_encode_fh(9)

okay so bestie, welcome to the Kernel API Manual — this one's exportfs_encode_fh(9) and it's literally the moment a dentry gets its glow-up into a file handle. no cap, it's a tiny page but it's doing the most. ✨

---

🌸 NAME 🌸

exportfs_encode_fh — encode a file handle from dentry

like… you hand it a dentry and it hands you back the encoded file handle. it's giving matchmaker energy fr fr. 💖

---

🎀 SYNOPSIS 🎀

int exportfs_encode_fh(struct dentry *dentry, struct fid *fid, int *max_len, int flags);

---

🦋 ARGUMENTS 🦋

• dentry — the object to encode. yeah, that's the whole vibe check right there, it's the thing going in. 👑
• fid — where to store the file handle fragment. this is the lil container that catches the output, bestie. 🎀
• max_len — maximum length to store there. a pointer to an int, so mind your limits — no overflowing the function's patience. 🙈
• flags — properties of the requested file handle. it's the customization slot, like choosing your handle's aesthetic. ✨

---

💜 DESCRIPTION 💜

Returns an enum fid_type, or a negative errno.

that's it, that's the whole description — short and iconic. so like, on the success side you get an enum fid_type back, and if things go sideways you get a negative errno instead. so always check your return value, bestie, don't just assume it ate. 🔥

---

🌈 SEE ALSO 🌈

• Kernel file ./fs/exportfs/expfs.c
• get_name(9) — related function, go look it up, iykyk 💅
• exportfs_encode_ino64_fid(9) — sibling function, same family tree ✨
• exportfs_encode_inode_fh(9) — another sibling, iconic trio honestly 🫶

---

lowkey reminder: max_len is a pointer, and it's the maximum length to store in fid — the docs are literally telling you the limit, so respect it. ⭐

---

and that's the page, bestie — written up in ./fs/exportfs, dated October 2026, from the Kernel API Manual. slay, periodt, go encode some file handles. 💖🎀🦋