[lkml]   [2000]   [Sep]   [14]   [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
On Thu, Sep 14, 2000 at 10:49:59AM +0200, Trond Myklebust wrote:
> >>>>> " " == Albert D Cahalan <> 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.

You could also just keep the more finegrained mtime in core and when
you flush the inode round it up to the next second.


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