From: Noveck, Dave (Dave.Noveck@netapp.com)
Date: 08/09/02-11:14:12 AM Z
Subject: RE: 32-bit servers and lock requests
Date: Fri, 9 Aug 2002 09:14:12 -0700
Message-ID: <8C610D86AF6CD4119C9800B0D0499E336A9000@red.nane.netapp.com>
From: "Noveck, Dave" <Dave.Noveck@netapp.com>
I blew it here. How about:
Some servers may only support locking for byte offsets that fit
within 32 bits. If the client specifies a range that includes a
byte beyond the last byte offset of the the 32-bit range, but does
not include the last byte offset of the 32-bit and all of the byte
offsets beyond it, up to the end of the valid 64-bit range, the
error NFS4ERR_BAD_RANGE will result.
Does that work?
-----Original Message-----
From: mike.kupfer@sun.com [mailto:mike.kupfer@sun.com]
Sent: Wednesday, August 07, 2002 1:07 PM
To: spencer.shepler@sun.com
Cc: nfsv4-wg@sunroof.eng.sun.com
Subject: 32-bit servers and lock requests
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
This archive was generated by hypermail 2.1.2 : 03/04/05-01:50:10 AM Z CST