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

From: Trond Myklebust (trond.myklebust@fys.uio.no)
Date: Wed Sep 13 2000 - 17:08:19 EST

Next message: Henner Eisen: "Re: Q: sock output serialization"
Previous message: Jeff V. Merkey: "Re: The case for a standard kernel debugger"
Next in thread: Trond Myklebust: "Re: NFS locking bug -- limited mtime resolution means nfs_lock() does not provide coherency guarantee"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

>>>>> " " == Andi Kleen <ak@suse.de> writes:

> Steal a couple of bytes from what ?

>From the 32-bit storage area currently allocated to i_generation on
the on-disk ext2fs inode (as per Ted's suggestion). With current
disk/computing speeds, you probably don't need the full 32 bits to
offer a reasonable guarantee of inode number uniqueness.

Cheers,
Trond
-
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: Henner Eisen: "Re: Q: sock output serialization"
Previous message: Jeff V. Merkey: "Re: The case for a standard kernel debugger"
Next in thread: Trond Myklebust: "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