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

From: Frank van Maarseveen (F.vanMaarseveen@inter.NL.net)
Date: Wed Sep 13 2000 - 15:37:31 EST

Next message: Torben Mathiasen: "Re: 2.4.0 SCSI doesn't compile without modules"
Previous message: Stephen Frazier: "RE: [ANNOUNCE] Darkstar Development Project"
In reply to: Trond Myklebust: "Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee"
Next in thread: Jeff Epler: "Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Wed, Sep 13, 2000 at 12:42:15PM +0200, Trond Myklebust wrote:
>
> Is there any 'standard' function for reading the microseconds fields
> in userland? I couldn't find anything with a brief search in the
> X/Open docs.
>
Both Digital OSF/1 and Solaris use 3 undocumented spare fields in the
struct stat and filled it with a microsecond/nanosecond fraction for
atime, mtime and ctime.

-- 
Frank
-
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/

Next message: Torben Mathiasen: "Re: 2.4.0 SCSI doesn't compile without modules"
Previous message: Stephen Frazier: "RE: [ANNOUNCE] Darkstar Development Project"
In reply to: Trond Myklebust: "Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee"
Next in thread: Jeff Epler: "Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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