From: Jeff Layton <jlayton@kernel.org>
To: NeilBrown <neilb@ownmail.net>, Chuck Lever <chuck.lever@oracle.com>
Cc: Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2] nfsd: discard nfserr_dropit
Date: Mon, 08 Sep 2025 15:33:45 -0400 [thread overview]
Message-ID: <569dc9ebd82418e77bf27762b1170fa7de1b2f5d.camel@kernel.org> (raw)
In-Reply-To: <175729544562.2850467.751680410529802310@noble.neil.brown.name>
On Mon, 2025-09-08 at 11:37 +1000, NeilBrown wrote:
> From: NeilBrown <neil@brown.name>
>
> 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>
> ---
>
> This version updated fo recent changes to fs/nfsd/lockd.c
>
> 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 6b042218668b..c774ce9aa296 100644
> --- a/fs/nfsd/lockd.c
> +++ b/fs/nfsd/lockd.c
> @@ -71,8 +71,6 @@ nlm_fopen(struct svc_rqst *rqstp, struct nfs_fh *f, struct file **filp,
> * to callback when the delegation is returned but might
> * not have a proper lock request to block on.
> */
> - fallthrough;
> - case nfserr_dropit:
> return nlm_drop_reply;
> case nfserr_stale:
> return nlm_stale_fh;
> diff --git a/fs/nfsd/nfsd.h b/fs/nfsd/nfsd.h
> index 1cd0bed57bc2..06e8327255f8 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 */
>
> base-commit: b8cf39957931982091e6446a98f151a79aeea07b
Reviewed-by: Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2025-09-08 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 1:37 [PATCH v2] nfsd: discard nfserr_dropit NeilBrown
2025-09-08 14:36 ` Chuck Lever
2025-09-08 19:33 ` Jeff Layton [this message]
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=569dc9ebd82418e77bf27762b1170fa7de1b2f5d.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@ownmail.net \
--cc=okorniev@redhat.com \
--cc=tom@talpey.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