nfsd_file_close_export(9)

💅 nfsd_file_close_export(9) 💅

Okay bestie, welcome to the nfsd_file_close_export(9) page from the Kernel API Manual. It's giving kernel-internals realness, and we're gonna get through it together. 🫶

---

🌸 NAME 🌸

nfsd_file_close_export — close cached file handles for an export

---

✨ SYNOPSIS ✨

void nfsd_file_close_export (struct net *net , const struct path *path
);

---

🎀 ARGUMENTS 🎀

• net — the net namespace in which to operate, iykyk.
• path — the export path whose cached files should be closed.

---

🦋 DESCRIPTION 🦋

So what it does is close out GC-managed nfsd_file entries whose underlying file is on the same filesystem as, and a descendant of, path. Slay. ✨

The thing is, nfsd_file entries do not carry an export reference, so the check uses the file's dentry ancestry. That's the vibe check it runs.

False positives — like closing a cached handle that did not originate from the target export — are harmless. The handle is simply reopened on the next access. No cap, it's fine. 💀

This is called from the NFSD_CMD_UNLOCK_EXPORT handler before revoking NFSv4 state, to ensure that cached file handles do not hold the filesystem busy. Main character energy: keeping the filesystem from being held hostage. 👑

---

🌈 SEE ALSO 🌈

Kernel file ./fs/nfsd/filecache.c

• nfsd_file_check_write_error(9)
• nfsd_file_put(9)
• nfsd_file_put_local(9)
• nfsd_file_file(9)
• nfsd_file_dispose_list_delayed(9)
• nfsd_file_net_dispose(9)
• nfsd_file_lru_cb(9)
• nfsd_file_cond_queue(9)
• nfsd_file_queue_for_close(9)
• nfsd_file_close_inode(9)
• nfsd_file_close_inode_sync(9)
• __nfsd_file_cache_purge(9)
• nfsd_file_cache_purge(9)
• nfsd_file_is_cached(9)
• nfsd_file_acquire_gc(9)
• nfsd_file_acquire(9)
• nfsd_file_acquire_local(9)
• nfsd_file_acquire_opened(9)
• nfsd_file_acquire_dir(9)
• nfsd_fsnotify_recalc_mask(9)

---

Signed off from ./fs/nfsd, dated October 2026, and the page is literally nfsd_file_close_export(9). Stay iconic, bestie. 💜🎀