From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nft PATCH 0/5] Fixes (and fallout) from running tests/monitor in JSON mode
Date: Tue, 2 Sep 2025 12:57:55 +0200 [thread overview]
Message-ID: <aLbNs-lZch_9BB01@orbyte.nwl.cc> (raw)
In-Reply-To: <20250829142513.4608-1-phil@nwl.cc>
On Fri, Aug 29, 2025 at 04:25:08PM +0200, Phil Sutter wrote:
> The reported problem of object deletion notifications with bogus data is
> resolved in patch four. It seems only object notifications were
> affected. Patch 6 extends test suite coverage for tables and chains a
> bit.
>
> Patch one is an unrelated trivial fix, patches two and three cover for
> oddities noticed while working on the actual problem.
>
> Phil Sutter (5):
> tools: gitignore nftables.service file
> monitor: Quote device names in chain declarations, too
Applied these two unrelated trivial fixes.
> mnl: Allow for updating devices on existing inet ingress hook chains
> monitor: Inform JSON printer when reporting an object delete event
> tests: monitor: Extend testcases a bit
>
> include/json.h | 5 +--
> src/evaluate.c | 6 ++--
> src/json.c | 18 ++++++----
> src/mnl.c | 2 ++
> src/monitor.c | 2 +-
> src/rule.c | 2 +-
> tests/monitor/testcases/chain.t | 41 ++++++++++++++++++++++
> tests/monitor/testcases/flowtable-simple.t | 12 +++++++
> tests/monitor/testcases/object.t | 10 +++---
> tests/monitor/testcases/table.t | 15 ++++++++
> tools/.gitignore | 1 +
> 11 files changed, 97 insertions(+), 17 deletions(-)
> create mode 100644 tests/monitor/testcases/chain.t
> create mode 100644 tests/monitor/testcases/table.t
> create mode 100644 tools/.gitignore
>
> --
> 2.51.0
>
>
>
next prev parent reply other threads:[~2025-09-02 10:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 14:25 [nft PATCH 0/5] Fixes (and fallout) from running tests/monitor in JSON mode Phil Sutter
2025-08-29 14:25 ` [nft PATCH 1/5] tools: gitignore nftables.service file Phil Sutter
2025-08-29 14:25 ` [nft PATCH 2/5] monitor: Quote device names in chain declarations, too Phil Sutter
2025-08-29 14:25 ` [nft PATCH 3/5] mnl: Allow for updating devices on existing inet ingress hook chains Phil Sutter
2025-09-08 10:29 ` Pablo Neira Ayuso
2025-09-08 11:01 ` Pablo Neira Ayuso
2025-09-08 23:48 ` Phil Sutter
2025-09-09 9:17 ` Pablo Neira Ayuso
2025-08-29 14:25 ` [nft PATCH 4/5] monitor: Inform JSON printer when reporting an object delete event Phil Sutter
2025-09-08 10:30 ` Pablo Neira Ayuso
2025-09-09 11:46 ` Phil Sutter
2025-08-29 14:25 ` [nft PATCH 5/5] tests: monitor: Extend testcases a bit Phil Sutter
2025-09-08 10:30 ` Pablo Neira Ayuso
2025-09-02 10:57 ` Phil Sutter [this message]
2025-09-11 16:05 ` [nft PATCH 0/5] Fixes (and fallout) from running tests/monitor in JSON mode 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=aLbNs-lZch_9BB01@orbyte.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