From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 0/3] Fix regression in auto port forwarding
Date: Fri, 21 Nov 2025 05:45:51 +0100 [thread overview]
Message-ID: <20251121054551.5c079b4c@elisabeth> (raw)
In-Reply-To: <20251119042634.2978171-1-david@gibson.dropbear.id.au>
On Wed, 19 Nov 2025 15:26:31 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> 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
Applied.
--
Stefano
prev parent reply other threads:[~2025-11-21 4:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 4:26 David Gibson
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 ` Stefano Brivio [this message]
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=20251121054551.5c079b4c@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
/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).