From: Carl Burnett (cburnett@us.ibm.com)
Date: 05/02/03-01:12:46 PM Z
Message-ID: <OFDEC0DF3F.C1A05476-ON87256D1A.00630A25@us.ibm.com> From: Carl Burnett <cburnett@us.ibm.com> Subject: [nfsv4] Clarification on READ with an all bits 1 stateid Date: Fri, 2 May 2003 13:12:46 -0500 From the spec, "For a READ with a stateid value of all bits 0, the server MAY allow the READ to be serviced subject to mandatory file locks or the current share deny modes for the file. For a READ with a stateid value of all bits 1, the server MAY allow READ operations to bypass locking checks at the server." In the all bits 1 case, does "bypass locking checks" mean oshare reservation checks and byte range lock checks if the server is a mandatory locking platform? I assume for a POSIX advisory locking platform, the byte range lock checks don't apply. Is anyone thinking of allowing the bypass of "locking checks" on all bits 1 in their server implementation. If "locking checks" also means oshare checks, doesn't it sort of defeat the feature of oshare reservations? Thanks, Carl Carl Burnett AIX Kernel Architecture - Distributed File Systems (512) 838-8498, TL 678-8498 (please reply to cburnett@us.ibm.com) _______________________________________________ nfsv4 mailing list nfsv4@ietf.org https://www1.ietf.org/mailman/listinfo/nfsv4
This archive was generated by hypermail 2.1.2 : 03/04/05-02:12:20 AM Z CST