[lkml]   [2000]   [Sep]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee
Trond Myklebust writes:

> Relying on the sub-second timing fields is a much more
> implementation-specific. It depends on the capabilities of both the
> filesystem and the server OS.
> Linux and the knfsd server code could easily be modified to provide
> such a service, but the problem (as I've stated before) is that you
> need to save the time somewhere on disk. I believe currently ext2
> provides only 32 bits of storage for mtime (though perhaps somebody
> else could comment on that).

Yes, ext2 has this limit.

It would not be reasonable to try extending ext2 to 64-bit times,
but milliseconds might be doable. You'd need 4 bytes to support
the 3 standard time stamps.

Going to microseconds would require 8 free bytes, which I don't
think we have. (but we do have more that one might think, due
to the unimplemented junk)

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

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