Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: bjschuma@netapp.com
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/3] NFSD: Update error codes
Date: Wed, 27 Aug 2014 13:59:10 -0400	[thread overview]
Message-ID: <20140827175910.GA13910@fieldses.org> (raw)
In-Reply-To: <1409152678-7806-2-git-send-email-bjschuma@netapp.com>

On Wed, Aug 27, 2014 at 11:17:56AM -0400, bjschuma@netapp.com wrote:
> From: Anna Schumaker <Anna.Schumaker@netapp.com>
> 
> Recent NFS v4.2 drafts have removed NFS4ERR_METADATA_NOTSUPP and
> reassigned the error code to NFS4ERR_UNION_NOTSUPP.

And these have no users, so fine.  Applying.

--b.

> 
> I also add in the NFS4ERR_OFFLOAD_NO_REQS error code.
> 
> Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
> ---
>  fs/nfsd/nfsd.h       | 2 +-
>  include/linux/nfs4.h | 3 ++-
>  2 files changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/nfsd/nfsd.h b/fs/nfsd/nfsd.h
> index 847daf3..747f3b95 100644
> --- a/fs/nfsd/nfsd.h
> +++ b/fs/nfsd/nfsd.h
> @@ -251,7 +251,7 @@ void		nfsd_lockd_shutdown(void);
>  #define nfserr_deleg_revoked		cpu_to_be32(NFS4ERR_DELEG_REVOKED)
>  #define nfserr_partner_notsupp		cpu_to_be32(NFS4ERR_PARTNER_NOTSUPP)
>  #define nfserr_partner_no_auth		cpu_to_be32(NFS4ERR_PARTNER_NO_AUTH)
> -#define nfserr_metadata_notsupp		cpu_to_be32(NFS4ERR_METADATA_NOTSUPP)
> +#define nfserr_union_notsupp		cpu_to_be32(NFS4ERR_UNION_NOTSUPP)
>  #define nfserr_offload_denied		cpu_to_be32(NFS4ERR_OFFLOAD_DENIED)
>  #define nfserr_wrong_lfs		cpu_to_be32(NFS4ERR_WRONG_LFS)
>  #define nfserr_badlabel		cpu_to_be32(NFS4ERR_BADLABEL)
> diff --git a/include/linux/nfs4.h b/include/linux/nfs4.h
> index a1e3064..79b2a0f 100644
> --- a/include/linux/nfs4.h
> +++ b/include/linux/nfs4.h
> @@ -235,10 +235,11 @@ enum nfsstat4 {
>  	/* nfs42 */
>  	NFS4ERR_PARTNER_NOTSUPP	= 10088,
>  	NFS4ERR_PARTNER_NO_AUTH	= 10089,
> -	NFS4ERR_METADATA_NOTSUPP = 10090,
> +	NFS4ERR_UNION_NOTSUPP = 10090,
>  	NFS4ERR_OFFLOAD_DENIED = 10091,
>  	NFS4ERR_WRONG_LFS = 10092,
>  	NFS4ERR_BADLABEL = 10093,
> +	NFS4ERR_OFFLOAD_NO_REQS = 10094,
>  };
>  
>  static inline bool seqid_mutating_err(u32 err)
> -- 
> 2.1.0
> 

  reply	other threads:[~2014-08-27 17:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27 15:17 [PATCH 0/3] NFSD: Add v4.2 SEEK support bjschuma
2014-08-27 15:17 ` [PATCH 1/3] NFSD: Update error codes bjschuma
2014-08-27 17:59   ` J. Bruce Fields [this message]
2014-08-27 15:17 ` [PATCH 2/3] NFSD: Create nfs v4.2 decode ops bjschuma
2014-08-27 17:42   ` Christoph Hellwig
2014-08-27 18:04     ` J. Bruce Fields
2014-08-27 15:17 ` [PATCH 3/3] NFSD: Implement SEEK bjschuma
2014-08-27 19:09   ` J. Bruce Fields
2014-08-27 19:21     ` Anna Schumaker
2014-08-27 19:29       ` J. Bruce Fields
2014-08-27 19:35       ` J. Bruce Fields
2014-08-27 19:39 ` [PATCH 0/3] NFSD: Add v4.2 SEEK support J. Bruce Fields

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140827175910.GA13910@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=bjschuma@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox