[lkml]   [2000]   [Sep]   [13]   [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:
> >>>>> " " == Albert D Cahalan <> writes:

>> 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)
> Don't forget that 2^20 > 10^6, hence if you really want units of
> microseconds, you actually only need to save 3 bytes worth of data
> per timestamp.

20 bits * 3 timestamps == 60 bits
60 bits <= 8 bytes

So you do need 8 bytes.

> For the purposes of NFS, however the 'microseconds' field doesn't
> actually have to mean anything. It's just used as a cookie.

I thought of this, but I don't think it is safe.

write to file X us=1
write to file Y us=1
write to file Y us=2
write to file Y us=3
write to file X us=2

Oops, "make" on some clients will think Y is newer than X.

Using the wrong unit would be OK, as long as it is a real
sub-second time unit that doesn't overflow... but then you
might as well convert it to microseconds.

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.169 / U:0.192 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site