From: Florian Westphal <fw@strlen.de>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: netdev@vger.kernel.org, jiri@resnulli.us, victor@mojatatu.com
Subject: Re: [PATCH net 0/4] net/sched: reset conntrack after packet munging
Date: Thu, 20 Aug 2026 13:44:29 +0200 [thread overview]
Message-ID: <aobonf659MB1Rc3c@strlen.de> (raw)
In-Reply-To: <CAM0EoMmaXyX+SMMLzE=6pka3p8a1EFatDX+L171XE6qGfTP+kQ@mail.gmail.com>
Jamal Hadi Salim <jhs@mojatatu.com> wrote:
> sorry, my brain wouldnt let it go: nf_confirm() looks very promising.
> I was tempted to create a patch and test it but i dont have time right now..
nf_confirm is the last hook in the conntrack pipeline, so not useful for
this -- all of the exposed code runs before this.
next prev parent reply other threads:[~2026-08-20 11:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 20:42 [PATCH net 0/4] net/sched: reset conntrack after packet munging Florian Westphal
2026-08-19 20:42 ` [PATCH net 1/4] selftests/tc-testing: pass mp_pm via initialiser Florian Westphal
2026-08-19 20:42 ` [PATCH net 2/4] net/sched: act_pedit: drop conntrack on network/transport header changes Florian Westphal
2026-08-19 20:42 ` [PATCH net 3/4] selftests: tc-testing: add act_ct test for ct reset handling Florian Westphal
2026-08-19 20:42 ` [PATCH net 4/4] net/sched: act_nat: discard any conntrack entry post modification Florian Westphal
2026-08-20 11:09 ` [PATCH net 0/4] net/sched: reset conntrack after packet munging Jamal Hadi Salim
2026-08-20 11:32 ` Jamal Hadi Salim
2026-08-20 11:44 ` Florian Westphal [this message]
2026-08-20 11:42 ` Florian Westphal
2026-08-20 11:58 ` Jamal Hadi Salim
2026-08-20 12:09 ` Florian Westphal
2026-08-20 12:41 ` Jamal Hadi Salim
2026-08-20 13:10 ` Florian Westphal
2026-08-20 16:54 ` Jamal Hadi Salim
2026-08-20 17:37 ` Florian Westphal
2026-08-20 19:02 ` Jamal Hadi Salim
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=aobonf659MB1Rc3c@strlen.de \
--to=fw@strlen.de \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=victor@mojatatu.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.