From: Jeff Layton <jlayton@kernel.org>
To: NeilBrown <neilb@suse.de>, Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org, Olga Kornievskaia <kolga@netapp.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Subject: Re: [PATCH 0/6] nfsd: assorted clean-ups
Date: Fri, 26 Jul 2024 08:50:13 -0400 [thread overview]
Message-ID: <6d0c68577601cea8edeefa1cfd30d99e44f5231f.camel@kernel.org> (raw)
In-Reply-To: <20240726022538.32076-1-neilb@suse.de>
On Fri, 2024-07-26 at 12:21 +1000, NeilBrown wrote:
> My recent series (that may not now be needed) to allow fh_verify() to
> not be given an rqstp pointer (instead taking the individual fields that
> it actually needs) exposed several opportunities for improving code
> cleanliness. This series provides just those.
>
> I'm not convinced that the last 2 are a genuine improvement, but that
> follow a pattern set by earlier patches, and maybe they are a good idea.
>
> There is some minor behavioural change in that some error codes are
> changed as described in patch 3.
>
> Thanks,
> NeilBrown
>
> [PATCH 1/6] nfsd: Don't pass all of rqst into rqst_exp_find()
> [PATCH 2/6] nfsd: Pass 'cred' instead of 'rqstp' to some functions.
> [PATCH 3/6] nfsd: Move error code mapping to per-version xdr code.
> [PATCH 4/6] nfsd: use nfsd_v4client() in nfsd_breaker_owns_lease()
> [PATCH 5/6] nfsd: further centralize protocol version checks.
> [PATCH 6/6] nfsd: move V4ROOT version check to nfsd_set_fh_dentry()
This all looks reasonable to me. The last two do seem more marginal
than the first four, but I think they make the code more readable, on
balance.
Reviewed-by: Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2024-07-26 12:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 2:21 [PATCH 0/6] nfsd: assorted clean-ups NeilBrown
2024-07-26 2:21 ` [PATCH 1/6] nfsd: Don't pass all of rqst into rqst_exp_find() NeilBrown
2024-07-26 2:21 ` [PATCH 2/6] nfsd: Pass 'cred' instead of 'rqstp' to some functions NeilBrown
2024-07-26 2:21 ` [PATCH 3/6] nfsd: Move error code mapping to per-version xdr code NeilBrown
2024-07-26 15:40 ` Chuck Lever
2024-07-26 22:07 ` NeilBrown
2024-07-27 16:25 ` Chuck Lever
2024-07-26 2:21 ` [PATCH 4/6] nfsd: use nfsd_v4client() in nfsd_breaker_owns_lease() NeilBrown
2024-07-26 2:21 ` [PATCH 5/6] nfsd: further centralize protocol version checks NeilBrown
2024-07-26 2:21 ` [PATCH 6/6] nfsd: move V4ROOT version check to nfsd_set_fh_dentry() NeilBrown
2024-07-26 12:50 ` 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=6d0c68577601cea8edeefa1cfd30d99e44f5231f.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=kolga@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--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