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

[Trond Myklebust]

>>>>> " " == Albert D Cahalan <[EMAIL PROTECTED]> writes:

     > The ext2 inode has 6 obviously free bytes, 6 that are only used
     > on filesystems marked as Hurd-type, and 8 that seem to be
     > claimed by competing security and EA projects. So, being
     > wasteful, it would be possible to have picoseconds on all 4
     > time stamps. Doing mere milliseconds on 3 timestamps would
     > leave us 16 bytes for security.

It's probably more realistic given the time resolution on most PCs.
One could perhaps allow for greater resolution on those filesystems
that have the storage for it at the VFS level.

What are the 'i_reserved'[12] fields all about?

Cheers,
  Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/