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 00/27] Convert server-side NFSv2 XDR to use xdrgen
Date: Thu, 17 Sep 2026 07:56:35 -0400 [thread overview]
Message-ID: <4edae19999311917fdc27b6a736a567bc6de249c.camel@kernel.org> (raw)
In-Reply-To: <20260916162859.2051-1-cel@kernel.org>
On Wed, 2026-09-16 at 12:28 -0400, Chuck Lever wrote:
> Replace NFSD's NFSv2 XDR encoders and decoders with code that is
> mechanically generated directly from the NFSv2 RPC language
> specification.
>
> The benefits for NFSv2 are marginal. When we eventually convert
> newer NFS versions to use xdrgen, I expect a reduction in human
> coding errors, improved spec compliance, and better memory safety
> for those more complex NFS programs.
>
> These patches have been lightly tested with fstests run against an
> xfs export.
>
> Chuck Lever (27):
> Documentation: Add the RPC language description of NFSv2
> NFSD: Add infrastructure for generating NFSv2 XDR encoders and
> decoders
> NFSD: Use xdrgen-generated NFSv2 protocol definitions
> NFSD: Remove '#include "xdr.h"' from fs/nfsd/xdr3.h
> NFSD: Relocate the NFSv2 XDR storage union into nfsproc.c
> NFSD: Use xdrgen XDR functions for the NFSv2 NULL procedure
> NFSD: Use xdrgen XDR functions for NFSv2 GETATTR procedure
> NFSD: Use xdrgen XDR functions for NFSv2 SETATTR procedure
> NFSD: Use xdrgen XDR functions for the NFSv2 ROOT procedure
> NFSD: Use xdrgen XDR functions for the NFSv2 LOOKUP procedure
> NFSD: Use xdrgen XDR functions for NFSv2 READLINK procedure
> NFSD: Use xdrgen XDR functions for NFSv2 READ procedure
> NFSD: Use xdrgen XDR functions for the NFSv2 WRITECACHE procedure
> NFSD: Use xdrgen XDR functions for NFSv2 WRITE procedure
> NFSD: Refactor nfsd_proc_create()
> NFSD: Use xdrgen XDR functions for NFSv2 CREATE procedure
> NFSD: Use xdrgen XDR functions for the NFSv2 REMOVE procedure
> NFSD: Use xdrgen XDR functions for the NFSv2 RENAME procedure
> NFSD: Use xdrgen XDR functions for the NFSv2 LINK procedure
> NFSD: Use xdrgen XDR functions for NFSv2 SYMLINK procedure
> NFSD: Use xdrgen XDR functions for NFSv2 MKDIR procedure
> NFSD: Use xdrgen XDR functions for NFSv2 RMDIR procedure
> NFSD: Use xdrgen XDR functions for the NFSv2 STATFS procedure
> NFSD: Use xdrgen XDR functions for NFSv2 READDIR arguments
> NFSD: Add a streaming directory reader
> NFSD: Refactor NFSv2 directory cookie encoding
> NFSD: Use xdrgen XDR functions for NFSv2 READDIR results
>
> Documentation/sunrpc/xdr/nfs2.x | 254 +++++
> fs/nfs_common/common.c | 5 +-
> fs/nfsd/Makefile | 15 +-
> fs/nfsd/nfs2acl.c | 2 +-
> fs/nfsd/nfs2xdr_gen.c | 1079 +++++++++++++++++++
> fs/nfsd/nfs2xdr_gen.h | 46 +
> fs/nfsd/nfs3xdr.c | 2 +
> fs/nfsd/nfsd.h | 2 -
> fs/nfsd/nfserr.h | 2 +-
> fs/nfsd/nfsfh.h | 5 +
> fs/nfsd/nfsproc.c | 1574 +++++++++++++++++++---------
> fs/nfsd/nfsxdr.c | 605 +++--------
> fs/nfsd/vfs.c | 239 +++--
> fs/nfsd/vfs.h | 40 +
> fs/nfsd/xdr.h | 167 +--
> fs/nfsd/xdr3.h | 3 +-
> include/linux/nfs_common.h | 4 +-
> include/linux/sunrpc/xdrgen/nfs2.h | 298 ++++++
> 18 files changed, 3121 insertions(+), 1221 deletions(-)
> create mode 100644 Documentation/sunrpc/xdr/nfs2.x
> create mode 100644 fs/nfsd/nfs2xdr_gen.c
> create mode 100644 fs/nfsd/nfs2xdr_gen.h
> create mode 100644 include/linux/sunrpc/xdrgen/nfs2.h
This all looks like a fairly sane and straightforward conversion, but
it's too much to review in detail. It's almost a shame to do this at a
time when we're talking about deprecating v2, but if it makes ongoing
maintenance easier, then I'm on board.
Also, there are 2 patches that were sent as part of this series, but
seem to be a separate series:
[PATCH v1 1/2] NFSD: map fh_verify() status codes for NFS_ACLv2 replies
[PATCH v1 2/2] NFSD: map fh_verify() status codes for NFS_ACLv3 replies
Did you mean to send those separately? In any case, for the 27-patch
series:
Acked-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2026-09-17 11:56 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 ` [PATCH v1 10/27] NFSD: Use xdrgen XDR functions for the NFSv2 LOOKUP procedure Chuck Lever
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 ` Jeff Layton [this message]
2026-09-17 14:57 ` [PATCH v1 00/27] Convert server-side NFSv2 XDR to use xdrgen 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=4edae19999311917fdc27b6a736a567bc6de249c.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