Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: NeilBrown <neil@brown.name>, Chuck Lever <chuck.lever@oracle.com>
Cc: Olga Kornievskaia <okorniev@redhat.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfsd: discard nfserr_dropit
Date: Thu, 21 Aug 2025 06:14:21 -0400	[thread overview]
Message-ID: <5f8113f8f8a4f92d0ab0b8450ca7297b2764f491.camel@kernel.org> (raw)
In-Reply-To: <175573864133.2234665.4220094746965657176@noble.neil.brown.name>

On Thu, 2025-08-21 at 11:10 +1000, NeilBrown wrote:
> 
> nfserr_dropit hasn't been used for over a decade, since rq_dropme and
> the RQ_DROPME were introduced.
> 
> Time to get rid of it completely.
> 
> Signed-off-by: NeilBrown <neil@brown.name>
> ---
>  fs/nfsd/lockd.c | 2 --
>  fs/nfsd/nfsd.h  | 8 +-------
>  2 files changed, 1 insertion(+), 9 deletions(-)
> 
> diff --git a/fs/nfsd/lockd.c b/fs/nfsd/lockd.c
> index edc9f75dc75c..dca80f5de0ad 100644
> --- a/fs/nfsd/lockd.c
> +++ b/fs/nfsd/lockd.c
> @@ -57,8 +57,6 @@ nlm_fopen(struct svc_rqst *rqstp, struct nfs_fh *f, struct file **filp,
>  	switch (nfserr) {
>  	case nfs_ok:
>  		return 0;
> -	case nfserr_dropit:
> -		return nlm_drop_reply;
>  	case nfserr_stale:
>  		return nlm_stale_fh;
>  	default:
> diff --git a/fs/nfsd/nfsd.h b/fs/nfsd/nfsd.h
> index 1cd0bed57bc2..2c9fa884ab05 100644
> --- a/fs/nfsd/nfsd.h
> +++ b/fs/nfsd/nfsd.h
> @@ -335,14 +335,8 @@ void		nfsd_lockd_shutdown(void);
>   * cannot conflict with any existing be32 nfserr value.
>   */
>  enum {
> -	NFSERR_DROPIT = NFS4ERR_FIRST_FREE,
> -/* if a request fails due to kmalloc failure, it gets dropped.
> - *  Client should resend eventually
> - */
> -#define	nfserr_dropit		cpu_to_be32(NFSERR_DROPIT)
> -
>  /* end-of-file indicator in readdir */
> -	NFSERR_EOF,
> +	NFSERR_EOF, = NFS4ERR_FIRST_FREE,
>  #define	nfserr_eof		cpu_to_be32(NFSERR_EOF)
>  
>  /* replay detected */

Modulo the extra comma...

Reviewed-by: Jeff Layton <jlayton@kernel.org>

  parent reply	other threads:[~2025-08-21 10:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-21  1:10 [PATCH] nfsd: discard nfserr_dropit NeilBrown
2025-08-21  3:50 ` NeilBrown
2025-08-21 10:14 ` Jeff Layton [this message]
2025-08-21 15:07 ` Chuck Lever

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=5f8113f8f8a4f92d0ab0b8450ca7297b2764f491.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=okorniev@redhat.com \
    /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