From: David Gibson <david@gibson.dropbear.id.au>
To: passt-dev@passt.top, Stefano Brivio <sbrivio@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH 0/3] Fix regression in auto port forwarding
Date: Wed, 19 Nov 2025 15:26:31 +1100 [thread overview]
Message-ID: <20251119042634.2978171-1-david@gibson.dropbear.id.au> (raw)
My recently merged series cleaning up the auto-port-forward scanning
contained a series bug: automatic forwards would only appear on
alternating seconds.
This turned out to be due to a fundamentally broken premise in my
thinking. I was thinking that for consistency we wanted the most
recent port map information throughout the process. But that's not
really true: for the purposes of exclusion what we really need to know
is which of the listening sockets we scan are ours. That's given by
the *prior* state of the forward maps, not the updated one based on a
new scan.
The series also had a number of worthwhile changes though. This
series fixes it up, by reverting the most misguided of the patches and
correcting behaviour of another one while preserving the accompanying
code re-orgs.
Link: https://bugs.passt.top/show_bug.cgi?id=176
David Gibson (3):
Revert "fwd: Update all port maps before applying exclusions"
fwd: Exclude ports based on prior mapping state
fwd: Don't explicitly exclude reverse-direction TCP ports for UDP
fwd.c | 44 ++++++++++++++++++++------------------------
1 file changed, 20 insertions(+), 24 deletions(-)
--
2.51.1
next reply other threads:[~2025-11-19 4:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 4:26 David Gibson [this message]
2025-11-19 4:26 ` [PATCH 1/3] Revert "fwd: Update all port maps before applying exclusions" David Gibson
2025-11-19 4:26 ` [PATCH 2/3] fwd: Exclude ports based on prior mapping state David Gibson
2025-11-19 4:26 ` [PATCH 3/3] fwd: Don't explicitly exclude reverse-direction TCP ports for UDP David Gibson
2025-11-21 4:45 ` [PATCH 0/3] Fix regression in auto port forwarding Stefano Brivio
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=20251119042634.2978171-1-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).