From: Florian Westphal <fw@strlen.de>
To: <netfilter-devel@vger.kernel.org>
Cc: Florian Westphal <fw@strlen.de>
Subject: [PATCH nft 0/2] src: add conntrack information to trace monitor mode
Date: Mon, 7 Jul 2025 11:47:12 +0200 [thread overview]
Message-ID: <20250707094722.2162-1-fw@strlen.de> (raw)
First patch is a preparation patch that moves the trace code
from netlink.c to the new trace.c file.
Second patch adds the ct info to the trace output.
This patch exposes the 'clash' bit to userspace.
(Technically its the kernel counterpart).
If you dislike this, I can send a kernel patch that removes
the bit before dumping ct status bits to userspace, let me
know.
Change since v1:
- prep patch to split to trace.c
- add ct status fields to data types
Florian Westphal (2):
src: split monitor trace code into new trace.c
src: add conntrack information to trace monitor mode
Makefile.am | 1 +
doc/data-types.txt | 31 +-
include/linux/netfilter/nf_conntrack_common.h | 16 +
include/netlink.h | 5 -
include/trace.h | 8 +
src/ct.c | 8 +
src/monitor.c | 2 +-
src/netlink.c | 332 -------------
src/trace.c | 462 ++++++++++++++++++
9 files changed, 512 insertions(+), 353 deletions(-)
create mode 100644 include/trace.h
create mode 100644 src/trace.c
--
2.49.0
next reply other threads:[~2025-07-07 9:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 9:47 Florian Westphal [this message]
2025-07-07 9:47 ` [PATCH nft 1/2] src: split monitor trace code into new trace.c Florian Westphal
2025-07-07 20:13 ` Pablo Neira Ayuso
2025-07-07 9:47 ` [PATCH nft 2/2] src: add conntrack information to trace monitor mode Florian Westphal
2025-07-07 19:02 ` [PATCH nft 0/2] " Pablo Neira Ayuso
2025-07-07 19:28 ` Florian Westphal
2025-07-07 20:14 ` Pablo Neira Ayuso
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=20250707094722.2162-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 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.