RE: [nfsv4] Error returns

Next message: Lisa Week: "Re: [nfsv4] NFSv4 ACLs: {READ,WRITE}_NAMED_ATTRIBUTES"
Previous message: J. Bruce Fields: "Re: [nfsv4] NFSv4 ACLs: {READ,WRITE}_NAMED_ATTRIBUTES"
Maybe in reply to: Fredric Isaman: "[nfsv4] Error returns"

Dave.Noveck@netapp.com

Subject: RE: [nfsv4] Error returns
Date: Wed, 15 Dec 2004 20:58:23 -0500
Message-ID: <C98692FD98048C41885E0B0FACD9DFB840D18A@exnane01.hq.netapp.com>
From: "Noveck, Dave" <Dave.Noveck@netapp.com>

> I noticed two cases where the RFC seems to state different error returns
> in different places for the same event, and was wondering if I could get
> some clarification.
> 
> Regarding an OPEN with a share conflict:
> Sect 8.9 -
>       if ((request.access & file_state.deny)) ||
>             (request.deny & file_state.access))
>                     return (NFS4ERR_DENIED)
>
>
> Sect 14.2.16 -
> "In the case that there is a existing SHARE reservation that conflicts
> with the OPEN request, the server returns the error NFS4ERR_SHARE_DENIED."

I believe SHARE_DENIED was a late addition (previously DENIED was used for
both this and denial because of a byte-range conflict).  So my guess is that
14.2.16 is correct and that 8.9 was just not updated to match.  Anybody else
know diferent (or the same)?

> Regarding a READ/WRITE that conflicts with a share reservation:
> Sect 8.1.4 -
> "the server must verify that the access mode allows writing and return an
> NFS4ERR_OPENMODE error if it does not"

If I, for example, open for read and then try to do a write using that stateid,
whether I (the principal) can write to that file or not, OPENMODE is
returned.

> Sect 14.2.16 -
> "If the requester is not authorized to READ or WRITE (depending on the
> share_access value), the server must return NFS4ERR_ACCESS."

If I try to open for write and am not allowed to write that file, ACCESS
is returned.

These are different situations.

_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org
https://www1.ietf.org/mailman/listinfo/nfsv4