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 0/5] xdrgen: Improve diagnostic reporting
Date: Sun, 12 Jul 2026 16:34:46 -0400 [thread overview]
Message-ID: <20260712203451.124902-1-cel@kernel.org> (raw)
Add missing detection and reporting for semantic errors specified in
RFCs 4506 and 5531.
Chuck Lever (5):
xdrgen: Align the error caret under tab-indented source
xdrgen: Record the source position of each declared identifier
xdrgen: Reject specifications that define a name twice
xdrgen: Enforce RFC 5531 name and number scoping for RPC programs
xdrgen: Reject out-of-range program, version, and procedure numbers
.../net/sunrpc/xdrgen/subcmds/declarations.py | 10 +-
.../net/sunrpc/xdrgen/subcmds/definitions.py | 7 +-
tools/net/sunrpc/xdrgen/subcmds/lint.py | 7 +-
tools/net/sunrpc/xdrgen/subcmds/source.py | 7 +-
.../tests/bad-procedure-number-negative.x | 20 ++
.../tests/bad-procedure-number-too-large.x | 20 ++
.../tests/bad-program-number-negative.x | 19 ++
.../tests/bad-program-number-too-large.x | 19 ++
.../tests/bad-version-number-negative.x | 19 ++
.../tests/bad-version-number-too-large.x | 19 ++
tools/net/sunrpc/xdrgen/xdr_ast.py | 290 +++++++++++++++---
tools/net/sunrpc/xdrgen/xdr_parse.py | 46 ++-
12 files changed, 428 insertions(+), 55 deletions(-)
create mode 100644 tools/net/sunrpc/xdrgen/tests/bad-procedure-number-negative.x
create mode 100644 tools/net/sunrpc/xdrgen/tests/bad-procedure-number-too-large.x
create mode 100644 tools/net/sunrpc/xdrgen/tests/bad-program-number-negative.x
create mode 100644 tools/net/sunrpc/xdrgen/tests/bad-program-number-too-large.x
create mode 100644 tools/net/sunrpc/xdrgen/tests/bad-version-number-negative.x
create mode 100644 tools/net/sunrpc/xdrgen/tests/bad-version-number-too-large.x
--
2.54.0
next reply other threads:[~2026-07-12 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 20:34 Chuck Lever [this message]
2026-07-12 20:34 ` [PATCH 1/5] xdrgen: Align the error caret under tab-indented source Chuck Lever
2026-07-12 20:34 ` [PATCH 2/5] xdrgen: Record the source position of each declared identifier Chuck Lever
2026-07-12 20:34 ` [PATCH 3/5] xdrgen: Reject specifications that define a name twice Chuck Lever
2026-07-12 20:34 ` [PATCH 4/5] xdrgen: Enforce RFC 5531 name and number scoping for RPC programs Chuck Lever
2026-07-12 20:34 ` [PATCH 5/5] xdrgen: Reject out-of-range program, version, and procedure numbers 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=20260712203451.124902-1-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.