diff options
| author | Frank Cusack <fcusack@fcusack.com> | 2003-06-09 03:11:00 -0700 |
|---|---|---|
| committer | Jaroslav Kysela <perex@suse.cz> | 2003-06-09 03:11:00 -0700 |
| commit | 32538906f50bd177cbf7f17ab0dbfa935ba2613d (patch) | |
| tree | eec64a78d6377049f49f4de59dee80712745d867 /include/linux/moduleparam.h | |
| parent | 78134d086ce1f01ba4321694444595f9f4ed388c (diff) | |
[PATCH] nfs_unlink() problem fix
When foo is unlinked, nfs_unlink() does a sillyrename, this puts the
dentry on nfs_delete_queue, and (in the VFS) unhashes it from the
dcache. This causes problems, since any later access to the
silly-renamed new .nfs file will create a NEW dentry that aliases the
one we originally created, but unhashed.
This causes various confusion, especially if we want to try to delete it
again later.
So fix this by not unhash the dentry after silly-renaming. In 2.2, each
fs was responsible for doing a d_delete(), in 2.4 and later it happens
in the VFS layer and I think it was just an oversight that the 2.4 VFS
doesn't consider sillyrename (considering the code and comments that are
cruft).
Also fixed up some comments while debugging this.
Diffstat (limited to 'include/linux/moduleparam.h')
0 files changed, 0 insertions, 0 deletions
