From: Chuck Lever <cel@kernel.org>
To: NeilBrown <neilb@ownmail.net>, 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>, Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH 0/3] Three xdrgen short subjects
Date: Fri, 26 Dec 2025 10:19:32 -0500 [thread overview]
Message-ID: <20251226151935.441045-1-cel@kernel.org> (raw)
From: Chuck Lever <chuck.lever@oracle.com>
While working on converting lockd to uses xdrgen, I noticed these
issues in the xdrgen tool.
Chuck Lever (3):
xdrgen: Extend error reporting to AST transformation phase
xdrgen: Emit a max_arg_sz macro
xdrgen: Add enum value validation to generated decoders
fs/nfsd/nfs4xdr_gen.c | 105 ++++++++++++++----
fs/nfsd/nfs4xdr_gen.h | 2 +-
include/linux/sunrpc/xdrgen/nfs4_1.h | 8 +-
tools/net/sunrpc/xdrgen/generators/enum.py | 9 +-
tools/net/sunrpc/xdrgen/generators/program.py | 35 +++++-
.../net/sunrpc/xdrgen/subcmds/declarations.py | 8 +-
.../net/sunrpc/xdrgen/subcmds/definitions.py | 10 +-
tools/net/sunrpc/xdrgen/subcmds/lint.py | 8 +-
tools/net/sunrpc/xdrgen/subcmds/source.py | 11 +-
.../xdrgen/templates/C/enum/decoder/enum.j2 | 11 ++
.../templates/C/enum/decoder/enum_be.j2 | 20 ++++
.../templates/C/program/maxsize/max_args.j2 | 3 +
tools/net/sunrpc/xdrgen/xdr_ast.py | 6 +-
tools/net/sunrpc/xdrgen/xdr_parse.py | 54 ++++++++-
tools/net/sunrpc/xdrgen/xdrgen | 6 +
15 files changed, 262 insertions(+), 34 deletions(-)
create mode 100644 tools/net/sunrpc/xdrgen/templates/C/program/maxsize/max_args.j2
--
2.52.0
next reply other threads:[~2025-12-26 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-26 15:19 Chuck Lever [this message]
2025-12-26 15:19 ` [PATCH 1/3] xdrgen: Extend error reporting to AST transformation phase Chuck Lever
2025-12-26 15:19 ` [PATCH 2/3] xdrgen: Emit a max_arg_sz macro Chuck Lever
2025-12-26 15:19 ` [PATCH 3/3] xdrgen: Add enum value validation to generated decoders Chuck Lever
2025-12-26 23:44 ` NeilBrown
2025-12-27 14:17 ` Chuck Lever
2025-12-27 23:02 ` NeilBrown
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=20251226151935.441045-1-cel@kernel.org \
--to=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=jlayton@kernel.org \
--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 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.