locking and 32-bit offsets (was "questions/comments on draft-ietf-nfsv4-rfc3010bis-02-04.txt")

New Message Reply About this list Date view Thread view Subject view Author view Attachment view

From: mike.kupfer@sun.com
Date: 08/12/02-03:08:26 PM Z 

Message-Id: <200208122008.g7CK8VXE107781@athyra.eng.sun.com>
From: mike.kupfer@sun.com
Subject: locking and 32-bit offsets (was "questions/comments on draft-ietf-nfsv4-rfc3010bis-02-04.txt")
Date: Mon, 12 Aug 2002 13:08:26 -0700

>>>>> "mre" == Mike Eisler <mike@eisler.com> writes:

    mre> Regarding,

    mre>      Some servers may only support locking for byte offsets
    mre>      that fit within 32 bits.  If the client specifies a
    mre>      range that includes a byte beyond the last byte offset
    mre>      of the the 32-bit range, but does not include the last
    mre>      byte offset of the 32-bit and all of the byte offsets
    mre>      beyond it, up to the end of the valid 64-bit range, such
    mre>      a 32-bit server MUST return the error NFS4ERR_BAD_RANGE.

    mre> I don't understand what the above is saying.

Let MAX32=0xffffffff.  If the client specifies a range that starts
after MAX32, a 32-bit server must return BAD_RANGE.  If the client
specifies a range that ends after MAX32 but before MAX64 ("end of
file"), a 32-bit server must return BAD_RANGE.

mike

New Message Reply About this list Date view Thread view Subject view Author view Attachment view

This archive was generated by hypermail 2.1.2 : 03/04/05-01:50:12 AM Z CST