From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever <cel@kernel.org>, NeilBrown <neil@brown.name>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v1 1/2] NFSD: Replace NFS3_ACCESS_FULL in nfsd4_access()
Date: Mon, 10 Aug 2026 13:23:39 -0400 [thread overview]
Message-ID: <8e3bdc70fce8138b11a69891983b646bf51dc8da.camel@kernel.org> (raw)
In-Reply-To: <20260810141900.33846-1-cel@kernel.org>
On Mon, 2026-08-10 at 10:18 -0400, Chuck Lever wrote:
> Clean up: Remove an NFSv3 constant (NFS3_ACCESS_FULL) used inside an
> NFSv4 code path.
>
> After this patch is applied, the nfs3.h header is no longer an
> implicit dependency of nfs4proc.c for this value. The definition
> itself stays in nfs3.h to avoid a kernel-user space API regression.
>
> Signed-off-by: Chuck Lever <cel@kernel.org>
> ---
> fs/nfsd/nfs4proc.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/fs/nfsd/nfs4proc.c b/fs/nfsd/nfs4proc.c
> index 03c32db618cd..a2bea8947ef5 100644
> --- a/fs/nfsd/nfs4proc.c
> +++ b/fs/nfsd/nfs4proc.c
> @@ -842,7 +842,9 @@ nfsd4_access(struct svc_rqst *rqstp, struct nfsd4_compound_state *cstate,
> struct nfsd4_access *access = &u->access;
> u32 access_full;
>
> - access_full = NFS3_ACCESS_FULL;
> + access_full = NFS4_ACCESS_READ | NFS4_ACCESS_LOOKUP |
> + NFS4_ACCESS_MODIFY | NFS4_ACCESS_EXTEND |
> + NFS4_ACCESS_DELETE | NFS4_ACCESS_EXECUTE;
> if (cstate->minorversion >= 2)
> access_full |= NFS4_ACCESS_XALIST | NFS4_ACCESS_XAREAD |
> NFS4_ACCESS_XAWRITE;
Reviewed-by: Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2026-08-10 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 14:18 [PATCH v1 1/2] NFSD: Replace NFS3_ACCESS_FULL in nfsd4_access() Chuck Lever
2026-08-10 14:19 ` [PATCH v1 2/2] NFSD: Move version-specific ACCESS maps into per-version code Chuck Lever
2026-08-10 17:23 ` Jeff Layton
2026-08-10 17:23 ` 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=8e3bdc70fce8138b11a69891983b646bf51dc8da.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=cel@kernel.org \
--cc=dai.ngo@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--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