[lkml]   [2003]   [Jun]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] nfs_unlink() race (was: nfs_refresh_inode: inode number mismatch)

On 11 Jun 2003, Alan Cox wrote:
> For vfat at least its all broken.

Looks like a different issue, not dentry aliasing per se.

> cd foo
> mv ../file .
> more file

Yes, VFAT ends up encoding the parent directory in the FH, so renaming
will invalidate the old file handle, and if you cache inodes (and thus
filehandles) over a directory move, badness happens.

Arguably it's a NFS client problem - the path revalidate at open time
should have caught the ESTALE and forced a new inode lookup. But I think
you can also argue that VFAT over NFS is just non-unixy enough that it
just isn't really "supported".

I think it's more of a "you can NFS-export strange filesystems for some
limited file sharing, but if things break, you get to keep both pieces".


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:36    [W:0.072 / U:1.284 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site