From: Florian Westphal <fw@strlen.de>
To: <netfilter-devel@vger.kernel.org>
Cc: Florian Westphal <fw@strlen.de>
Subject: [PATCH nft 0/6] Misc parser fixes
Date: Mon, 19 Jun 2023 22:43:00 +0200 [thread overview]
Message-ID: <20230619204306.11785-1-fw@strlen.de> (raw)
These patches fix various bugs in the parsing
and evaluation steps.
I added a new 'bogons' test dir to shell, this can be used
to collect invalid inputs that should be rejected instead
of nft exiting with an assertion failure.
Florian Westphal (6):
json: dccp: remove erroneous const qualifier
evaluate: do not abort when prefix map has non-map element
parser: don't assert on scope underflows
parser: reject zero-length interface names
parser: reject zero-length interface names in flowtables
ct timeout: fix 'list object x' vs. 'list objects in table' confusion
include/rule.h | 1 +
src/cache.c | 1 +
src/evaluate.c | 18 ++++--
src/parser_bison.y | 61 ++++++++++++++-----
src/parser_json.c | 2 +-
src/rule.c | 1 +
tests/shell/testcases/bogons/assert_failures | 12 ++++
.../nat_prefix_map_with_set_element_assert | 7 +++
.../bogons/nft-f/scope_underflow_assert | 6 ++
.../nft-f/zero_length_devicename_assert | 5 ++
.../zero_length_devicename_flowtable_assert | 5 ++
11 files changed, 98 insertions(+), 21 deletions(-)
create mode 100755 tests/shell/testcases/bogons/assert_failures
create mode 100644 tests/shell/testcases/bogons/nft-f/nat_prefix_map_with_set_element_assert
create mode 100644 tests/shell/testcases/bogons/nft-f/scope_underflow_assert
create mode 100644 tests/shell/testcases/bogons/nft-f/zero_length_devicename_assert
create mode 100644 tests/shell/testcases/bogons/nft-f/zero_length_devicename_flowtable_assert
--
2.39.3
next reply other threads:[~2023-06-19 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 20:43 Florian Westphal [this message]
2023-06-19 20:43 ` [PATCH nft 1/6] json: dccp: remove erroneous const qualifier Florian Westphal
2023-06-19 20:43 ` [PATCH nft 2/6] evaluate: do not abort when prefix map has non-map element Florian Westphal
2023-06-19 20:43 ` [PATCH nft 3/6] parser: don't assert on scope underflows Florian Westphal
2023-06-19 20:43 ` [PATCH nft 4/6] parser: reject zero-length interface names Florian Westphal
2023-06-20 16:02 ` Pablo Neira Ayuso
2023-06-19 20:43 ` [PATCH nft 5/6] parser: reject zero-length interface names in flowtables Florian Westphal
2023-06-19 20:43 ` [PATCH nft 6/6] ct timeout: fix 'list object x' vs. 'list objects in table' confusion Florian Westphal
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=20230619204306.11785-1-fw@strlen.de \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).