Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee

From: Trond Myklebust (trond.myklebust@fys.uio.no)
Date: Wed Sep 13 2000 - 07:53:02 EST


>>>>> " " == Jamie Lokier <lk@tantalophile.demon.co.uk> writes:

> If we're getting serious about adding finer-grained mtimes to
> ext2, could we please consider using those bits as a way to
> know, for sure, whether a file has changed?

Agreed.

> Btw, the whole cache coherency thing would probably work very
> well just updating times in in-core inodes.

No. Things fall in and out of the inode cache all the time. That's a
vicious circle that's going to lead to a lot of unnecessary traffic.

Cheers,
  Trond
-
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/



This archive was generated by hypermail 2b29 : Fri Sep 15 2000 - 21:00:20 EST