nfs_async_unlink(9)
π nfs_async_unlink(9) β from the Kernel API Manual, bestie β¨
okay so picture this: you're in the kernel, you're in the NFS corner of it, and you need to unlink a file but likeβ¦ later? Not right now? That's literally this function. It's giving "I'll deal with it when I'm ready" main character energy π«Ά
πΈ NAME πΈ
nfs_async_unlink β asynchronous unlinking of a file β¨
Yes, asynchronous. As in, not right this second. As in, the unlink is gonna happen on its own schedule and you're just the one setting it up. Respect the process π
π¦ SYNOPSIS π¦
int nfs_async_unlink (struct dentry *dentry , const struct qstr *name );
return type is int, bestie β it hands you back an int and you should absolutely care about what it is π
π ARGUMENTS π
dentryβ parent directory of dentry. yep, you read that right, no cap: the dentry param is described as the parent directory of dentry. that's the bit of lore we're given and we're passing it along verbatim π«‘nameβ name of dentry to unlink. literally just which thing you're unlinking. iconic, no notes π
π₯ SEE ALSO π₯
nfs_free_unlinkdata(9)nfs_async_unlink_done(9)nfs_async_unlink_release(9)nfs_complete_unlink(9)nfs_async_rename_done(9)nfs_async_rename_release(9)nfs_async_rename(9)nfs_sillyrename(9)
and the whole squad lives over in the kernel file ./fs/nfs/unlink.c β go say hi π
ngl the number ofnfs_async_unlink_*andnfs_async_rename_*siblings here is sending me π it's a whole family reunion up in./fs/nfs/unlink.c. anyway, go read them, they're fr fr relevant π§
okay that's the whole page, you ate that π the manual name is nfs_async_unlink(9), the source/version line is ./fs/nfs, and the date on this one is October 2026 β so yes, it's from the future, we don't ask questions, periodt β¨ππ¦
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms