nfs_async_rename(9)

🌸 nfs_async_rename 💅

okay bestie, so this one's from the Kernel API Manual and it's literally the NFS girlies' guide to doing a rename asynchronously — like, not right now, but the kernel's got it handled, trust. 🦋

✨ NAME ✨

nfs_async_rename — perform an asynchronous rename operation, no cap 💖

🎀 SYNOPSIS 🎀

struct rpc_task * nfs_async_rename (struct inode *old_dir , struct inode
*new_dir , struct dentry *old_dentry , struct dentry *new_dentry , void
(*complete)(struct rpc_task *, struct nfs_renamedata *) );

like… it returns a struct rpc_task *, she's giving main character energy fr fr 🔥

🧚 ARGUMENTS 🧚

• old_dir — the directory that currently holds the dentry you wanna rename. like, where she lives rn 🏠
• new_dir — the target directory for the rename. the destination, the glow-up location ✨
• old_dentry — the original dentry to be renamed. the before pic 💅
• new_dentry — the dentry that old_dentry should be renamed to. the after pic 🎀
• complete — Function to run on successful completion. yes bestie, it's a callback: void (*complete)(struct rpc_task *, struct nfs_renamedata *) — she gets called when things go right 🫶

🌈 DESCRIPTION 🌈

It's expected that valid references to the dentries and inodes are held.

ngl that's the whole description 😭 but it matters!! valid refs on the dentries and the inodes, held, periodt. do not come for this function without them 💀

👑 SEE ALSO 👑

bestie, go read these too, iykyk:

• Kernel file ./fs/nfs/unlink.c
• nfs_free_unlinkdata(9)
• nfs_async_unlink_done(9)
• nfs_async_unlink_release(9)
• nfs_async_unlink(9)
• nfs_complete_unlink(9)
• nfs_async_rename_done(9)
• nfs_async_rename_release(9)
• nfs_sillyrename(9)

okay that's the whole page, you ate that 🍓 mwah 💋 — this came from ./fs/nfs, dated October 2026, in the Kernel API Manual, and nfs_async_rename(9) is literally the title of the whole thing. slay 🌟