From: Florian Westphal <fw@strlen.de>
To: <netfilter-devel@vger.kernel.org>
Cc: Florian Westphal <fw@strlen.de>
Subject: [PATCH nf 0/2] netfilter: nf_nat: fix yet another bizarre early demux corner case
Date: Tue, 15 Aug 2023 11:52:39 +0200 [thread overview]
Message-ID: <20230815095245.9386-1-fw@strlen.de> (raw)
There is another corner case where early demux can end up assigning
the wrong socket to skb->sk.
This extends the existing workaround in nf_nat and the test case
to demonstrate the problem.
Florian Westphal (2):
netfilter: nf_nat: undo erroneous tcp edemux lookup after port clash
selftests: netfilter: test nat source port clash resolution
interaction with tcp early demux
net/netfilter/nf_nat_proto.c | 63 ++++++++++++++++++-
.../selftests/netfilter/nf_nat_edemux.sh | 46 +++++++++++---
2 files changed, 97 insertions(+), 12 deletions(-)
--
2.41.0
next reply other threads:[~2023-08-15 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 9:52 Florian Westphal [this message]
2023-08-15 9:52 ` [PATCH nf 1/2] netfilter: nf_nat: undo erroneous tcp edemux lookup after port clash Florian Westphal
2023-08-15 9:52 ` [PATCH nf 2/2] selftests: netfilter: test nat source port clash resolution interaction with tcp early demux 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=20230815095245.9386-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).