Linux Netfilter development
 help / color / mirror / Atom feed
From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: [nft PATCH v2 0/5] json: Accept more than two operands in binary expressions
Date: Fri, 22 Mar 2024 17:06:40 +0100	[thread overview]
Message-ID: <20240322160645.18331-1-phil@nwl.cc> (raw)

This needed rebase of patch 1 to cover for intermediate changes got a
bit out of hand and resulted in this series:

Patch 2 fixes a bug in set element sorting triggered by binop expression
elements being treated equal in value if the LHS parts match.

Patch 3 collates general bugs in recorded JSON equivalents for py
testsuite.

Patch 4 adds detection of needless recorded JSON outputs to
nft-tests.py, patch 5 then performs the cleanup to eliminate the
warnings it generates.

Phil Sutter (5):
  json: Accept more than two operands in binary expressions
  mergesort: Avoid accidental set element reordering
  tests: py: Fix some JSON equivalents
  tests: py: Warn if recorded JSON output matches the input
  tests: py: Drop needless recorded JSON outputs

 doc/libnftables-json.adoc                     |  18 +-
 src/intervals.c                               |   2 +-
 src/json.c                                    |  19 +-
 src/mergesort.c                               |   2 +-
 src/parser_json.c                             |  12 +
 tests/py/any/last.t.json.output               |   7 -
 tests/py/any/meta.t.json                      |   2 +-
 tests/py/any/meta.t.json.output               | 180 ----------
 tests/py/any/tcpopt.t.json                    |   4 +-
 tests/py/inet/tcp.t.json                      | 189 ++++------
 tests/py/inet/tcp.t.json.output               | 339 +-----------------
 tests/py/ip/numgen.t.json.output              |  30 --
 tests/py/ip6/exthdr.t.json.output             |  30 --
 tests/py/nft-test.py                          |   2 +
 .../dumps/0012different_defines_0.json-nft    |   8 +-
 .../sets/dumps/0055tcpflags_0.json-nft        | 114 ++----
 .../testcases/sets/dumps/0055tcpflags_0.nft   |   8 +-
 17 files changed, 166 insertions(+), 800 deletions(-)

-- 
2.43.0


             reply	other threads:[~2024-03-22 16:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22 16:06 Phil Sutter [this message]
2024-03-22 16:06 ` [nft PATCH v2 1/5] json: Accept more than two operands in binary expressions Phil Sutter
2024-03-22 16:06 ` [nft PATCH v2 2/5] mergesort: Avoid accidental set element reordering Phil Sutter
2024-03-22 16:06 ` [nft PATCH v2 3/5] tests: py: Fix some JSON equivalents Phil Sutter
2024-03-22 16:06 ` [nft PATCH v2 4/5] tests: py: Warn if recorded JSON output matches the input Phil Sutter
2024-03-22 16:06 ` [nft PATCH v2 5/5] tests: py: Drop needless recorded JSON outputs Phil Sutter
2024-04-12 12:35 ` [nft PATCH v2 0/5] json: Accept more than two operands in binary expressions Phil Sutter

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=20240322160645.18331-1-phil@nwl.cc \
    --to=phil@nwl.cc \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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