32-bit servers and lock requests

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

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


Message-Id: <200208071707.g77H7NXE959472@athyra.eng.sun.com>
From: mike.kupfer@sun.com
Subject: 32-bit servers and lock requests
Date: Wed, 07 Aug 2002 10:07:18 -0700

Section 14.2.10 (LOCK) of the latest I-D says

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

This wording says that if the client submits any of the following lock
requests, the server must return NFS4ERR_BAD_RANGE.

    (offset=0xffffffff, length=1)
    (offset=0xfffffffe, length=2)
    (offset=0, length=0xffffffff)

Why *must* the server (even a 32-bit server) return an error here?

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:09 AM Z CST