Messages in this thread | | | Date | Wed, 13 Sep 2000 23:14:52 +0200 | From | "Andi Kleen" <> | Subject | Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee |
| |
On Wed, Sep 13, 2000 at 10:35:10PM +0200, Trond Myklebust wrote: > > No, it does not help. i_generation is only in the NFS file > > handle, but not in the fattr/file id this is used for cache > > checks. The NFS file handle has to stay identical anyways, as > > long as the inode is not deleted/reused. > > > You might be able to steal a couple of bytes and then rewrite ext2fs > to mask those out from the 'i_generation' field, but it would mean that > you could no longer boot your old 2.2.16 kernel without trouble on > existing clients.
Steal a couple of bytes from what ?
-Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
| |