From: Chuck Lever <cel@kernel.org>
To: NeilBrown <neil@brown.name>, Jeff Layton <jlayton@kernel.org>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>
Cc: <linux-nfs@vger.kernel.org>
Subject: [PATCH v1 10/27] NFSD: Use xdrgen XDR functions for the NFSv2 LOOKUP procedure
Date: Wed, 16 Sep 2026 12:28:41 -0400 [thread overview]
Message-ID: <20260916162859.2051-13-cel@kernel.org> (raw)
In-Reply-To: <20260916162859.2051-1-cel@kernel.org>
Replace the NFSPROC_LOOKUP entry in the nfsd_procedures2 array
with an entry that dispatches the xdrgen-generated
nfs_svc_decode_diropargs and nfs_svc_encode_diropres. Wrapper
structures bridge the generated xdrgen types and the legacy
svc_fh and kstat representations the NFSD VFS layer still uses.
The pc_argzero field is now set to zero for the NFSv2 LOOKUP
procedure. The xdrgen decoders are trusted to initialize all
arguments in the argp->xdrgen field, making the early defensive
memset unnecessary. The remaining argp fields are cleared as
needed.
This refactor replaces the use of svcxdr_encode_fattr(), so the
references to the directory and object file handles can be
released directly by nfsd_proc_lookup(). A separate ->pc_release
callback is thus no longer needed. This makes it straightforward
to confirm that the file handles are properly released during
every error flow.
Signed-off-by: Chuck Lever <cel@kernel.org>
---
fs/nfsd/nfsproc.c | 95 ++++++++++++++++++++++++++++++++---------------
1 file changed, 65 insertions(+), 30 deletions(-)
diff --git a/fs/nfsd/nfsproc.c b/fs/nfsd/nfsproc.c
index c0f8c6988925..ce52939b3ae7 100644
--- a/fs/nfsd/nfsproc.c
+++ b/fs/nfsd/nfsproc.c
@@ -48,6 +48,21 @@ struct sattrargs_wrapper {
static_assert(offsetof(struct sattrargs_wrapper, xdrgen) == 0);
+struct diropargs_wrapper {
+ struct diropargs xdrgen;
+ struct svc_fh fh;
+};
+
+static_assert(offsetof(struct diropargs_wrapper, xdrgen) == 0);
+
+struct diropres_wrapper {
+ struct diropres xdrgen;
+ struct svc_fh fh;
+ struct kstat stat;
+};
+
+static_assert(offsetof(struct diropres_wrapper, xdrgen) == 0);
+
static __be32 nfsd_map_status(__be32 status)
{
switch (status) {
@@ -81,6 +96,12 @@ nfsd_fhandle_to_svc_fh(struct svc_fh *fhp, const fhandle *fhandle)
memcpy(&fhp->fh_handle.fh_raw, fhandle, NFS_FHSIZE);
}
+static __always_inline void
+nfsd_svc_fh_to_fhandle(fhandle *fhandle, const struct svc_fh *fhp)
+{
+ memcpy(fhandle, fhp->fh_handle.fh_raw, NFS_FHSIZE);
+}
+
static __always_inline void
nfsd_timespec64_to_timeval(struct timeval *dst,
const struct timespec64 *src)
@@ -412,31 +433,46 @@ static __be32 nfsd_proc_root(struct svc_rqst *rqstp)
return rpc_success;
}
-/*
- * Look up a path name component
- * Note: the dentry in the resp->fh may be negative if the file
- * doesn't exist yet.
- * N.B. After this call resp->fh needs an fh_put
+/**
+ * nfsd_proc_lookup - LOOKUP: Look up file name
+ * @rqstp: RPC transaction context
+ *
+ * Return:
+ * %rpc_success: RPC executed successfully
+ *
+ * RPC synopsis:
+ * diropres NFSPROC_LOOKUP(diropargs) = 4;
*/
-static __be32
-nfsd_proc_lookup(struct svc_rqst *rqstp)
+static __be32 nfsd_proc_lookup(struct svc_rqst *rqstp)
{
- struct nfsd_diropargs *argp = rqstp->rq_argp;
- struct nfsd_diropres *resp = rqstp->rq_resp;
+ struct diropargs_wrapper *argp = rqstp->rq_argp;
+ struct diropres_wrapper *resp = rqstp->rq_resp;
+ struct diropargs *what = &argp->xdrgen;
+ struct kstat *statp = &resp->stat;
+ struct svc_fh *dirfhp = &argp->fh;
+ struct svc_fh *fhp = &resp->fh;
- dprintk("nfsd: LOOKUP %s %.*s\n",
- SVCFH_fmt(&argp->fh), argp->len, argp->name);
+ nfsd_fhandle_to_svc_fh(dirfhp, &what->dir);
- fh_init(&resp->fh, NFS_FHSIZE);
- resp->status = nfsd_lookup(rqstp, &argp->fh, argp->name, argp->len,
- &resp->fh);
- fh_put(&argp->fh);
- if (resp->status != nfs_ok)
+ fh_init(fhp, NFS_FHSIZE);
+ resp->xdrgen.status = nfsd_lookup(rqstp, dirfhp,
+ (char *)what->name.data,
+ what->name.len, fhp);
+ if (resp->xdrgen.status != nfs_ok)
goto out;
+ resp->xdrgen.status = fh_getattr(fhp, statp);
- resp->status = fh_getattr(&resp->fh, &resp->stat);
out:
- resp->status = nfsd_map_status(resp->status);
+ if (resp->xdrgen.status == nfs_ok) {
+ nfsd_svc_fh_to_fhandle(&resp->xdrgen.u.diropok.file, fhp);
+ nfsd_stat_to_fattr(rqstp, &resp->xdrgen.u.diropok.attributes,
+ statp, fhp);
+ } else {
+ resp->xdrgen.status = nfsd_map_status(resp->xdrgen.status);
+ }
+
+ fh_put(fhp);
+ fh_put(dirfhp);
return rpc_success;
}
@@ -957,16 +993,15 @@ static const struct svc_procedure nfsd_procedures2[18] = {
.pc_name = "ROOT",
},
[NFSPROC_LOOKUP] = {
- .pc_func = nfsd_proc_lookup,
- .pc_decode = nfssvc_decode_diropargs,
- .pc_encode = nfssvc_encode_diropres,
- .pc_release = nfssvc_release_diropres,
- .pc_argsize = sizeof(struct nfsd_diropargs),
- .pc_argzero = sizeof(struct nfsd_diropargs),
- .pc_ressize = sizeof(struct nfsd_diropres),
- .pc_cachetype = RC_NOCACHE,
- .pc_xdrressize = ST+FH+AT,
- .pc_name = "LOOKUP",
+ .pc_func = nfsd_proc_lookup,
+ .pc_decode = nfs_svc_decode_diropargs,
+ .pc_encode = nfs_svc_encode_diropres,
+ .pc_argsize = sizeof(struct diropargs_wrapper),
+ .pc_argzero = 0,
+ .pc_ressize = sizeof(struct diropres_wrapper),
+ .pc_cachetype = RC_NOCACHE,
+ .pc_xdrressize = NFS2_diropres_sz,
+ .pc_name = "LOOKUP",
},
[NFSPROC_READLINK] = {
.pc_func = nfsd_proc_readlink,
@@ -1122,7 +1157,7 @@ static const struct svc_procedure nfsd_procedures2[18] = {
union nfsd_xdrstore {
struct fhandle_wrapper fhandle;
struct sattrargs_wrapper sattrargs;
- struct nfsd_diropargs dirop;
+ struct diropargs_wrapper diropargs;
struct nfsd_readargs read;
struct nfsd_writeargs write;
struct nfsd_createargs create;
@@ -1131,7 +1166,7 @@ union nfsd_xdrstore {
struct nfsd_symlinkargs symlink;
struct nfsd_readdirargs readdir;
struct attrstat_wrapper attrstat;
- struct nfsd_diropres diropres;
+ struct diropres_wrapper diropres;
struct nfsd_readlinkres readlinkres;
struct nfsd_readres readres;
struct nfsd_readdirres readdirres;
--
2.55.0
next prev parent reply other threads:[~2026-09-16 16:29 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 16:28 [PATCH v1 00/27] Convert server-side NFSv2 XDR to use xdrgen Chuck Lever
2026-09-16 16:28 ` [PATCH v1 01/27] Documentation: Add the RPC language description of NFSv2 Chuck Lever
2026-09-16 16:28 ` [PATCH v1 1/2] NFSD: map fh_verify() status codes for NFS_ACLv2 replies Chuck Lever
2026-09-17 11:57 ` Jeff Layton
2026-09-16 16:28 ` [PATCH v1 02/27] NFSD: Add infrastructure for generating NFSv2 XDR encoders and decoders Chuck Lever
2026-09-16 16:28 ` [PATCH v1 2/2] NFSD: map fh_verify() status codes for NFS_ACLv3 replies Chuck Lever
2026-09-17 11:57 ` Jeff Layton
2026-09-16 16:28 ` [PATCH v1 03/27] NFSD: Use xdrgen-generated NFSv2 protocol definitions Chuck Lever
2026-09-16 16:28 ` [PATCH v1 04/27] NFSD: Remove '#include "xdr.h"' from fs/nfsd/xdr3.h Chuck Lever
2026-09-16 16:28 ` [PATCH v1 05/27] NFSD: Relocate the NFSv2 XDR storage union into nfsproc.c Chuck Lever
2026-09-16 16:28 ` [PATCH v1 06/27] NFSD: Use xdrgen XDR functions for the NFSv2 NULL procedure Chuck Lever
2026-09-16 16:28 ` [PATCH v1 07/27] NFSD: Use xdrgen XDR functions for NFSv2 GETATTR procedure Chuck Lever
2026-09-16 16:28 ` [PATCH v1 08/27] NFSD: Use xdrgen XDR functions for NFSv2 SETATTR procedure Chuck Lever
2026-09-16 16:28 ` [PATCH v1 09/27] NFSD: Use xdrgen XDR functions for the NFSv2 ROOT procedure Chuck Lever
2026-09-16 16:28 ` Chuck Lever [this message]
2026-09-16 16:28 ` [PATCH v1 11/27] NFSD: Use xdrgen XDR functions for NFSv2 READLINK procedure Chuck Lever
2026-09-16 16:28 ` [PATCH v1 12/27] NFSD: Use xdrgen XDR functions for NFSv2 READ procedure Chuck Lever
2026-09-16 16:28 ` [PATCH v1 13/27] NFSD: Use xdrgen XDR functions for the NFSv2 WRITECACHE procedure Chuck Lever
2026-09-16 16:28 ` [PATCH v1 14/27] NFSD: Use xdrgen XDR functions for NFSv2 WRITE procedure Chuck Lever
2026-09-16 16:28 ` [PATCH v1 15/27] NFSD: Refactor nfsd_proc_create() Chuck Lever
2026-09-16 16:28 ` [PATCH v1 16/27] NFSD: Use xdrgen XDR functions for NFSv2 CREATE procedure Chuck Lever
2026-09-16 16:28 ` [PATCH v1 17/27] NFSD: Use xdrgen XDR functions for the NFSv2 REMOVE procedure Chuck Lever
2026-09-16 16:28 ` [PATCH v1 18/27] NFSD: Use xdrgen XDR functions for the NFSv2 RENAME procedure Chuck Lever
2026-09-16 16:28 ` [PATCH v1 19/27] NFSD: Use xdrgen XDR functions for the NFSv2 LINK procedure Chuck Lever
2026-09-16 16:28 ` [PATCH v1 20/27] NFSD: Use xdrgen XDR functions for NFSv2 SYMLINK procedure Chuck Lever
2026-09-16 16:28 ` [PATCH v1 21/27] NFSD: Use xdrgen XDR functions for NFSv2 MKDIR procedure Chuck Lever
2026-09-16 16:28 ` [PATCH v1 22/27] NFSD: Use xdrgen XDR functions for NFSv2 RMDIR procedure Chuck Lever
2026-09-16 16:28 ` [PATCH v1 23/27] NFSD: Use xdrgen XDR functions for the NFSv2 STATFS procedure Chuck Lever
2026-09-16 16:28 ` [PATCH v1 24/27] NFSD: Use xdrgen XDR functions for NFSv2 READDIR arguments Chuck Lever
2026-09-16 16:28 ` [PATCH v1 25/27] NFSD: Add a streaming directory reader Chuck Lever
2026-09-16 16:28 ` [PATCH v1 26/27] NFSD: Refactor NFSv2 directory cookie encoding Chuck Lever
2026-09-16 16:28 ` [PATCH v1 27/27] NFSD: Use xdrgen XDR functions for NFSv2 READDIR results Chuck Lever
2026-09-17 11:56 ` [PATCH v1 00/27] Convert server-side NFSv2 XDR to use xdrgen Jeff Layton
2026-09-17 14:57 ` 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=20260916162859.2051-13-cel@kernel.org \
--to=cel@kernel.org \
--cc=dai.ngo@oracle.com \
--cc=jlayton@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.