From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 7/8] fwd: Update all port maps before applying exclusions
Date: Fri, 31 Oct 2025 13:51:39 +1100 [thread overview]
Message-ID: <aQQkOwgXuBIbgR0j@zatzit> (raw)
In-Reply-To: <20251030212407.66e07446@elisabeth>
[-- Attachment #1: Type: text/plain, Size: 2002 bytes --]
On Thu, Oct 30, 2025 at 09:24:07PM +0100, Stefano Brivio wrote:
> On Sat, 11 Oct 2025 15:48:26 +1100
> David Gibson <david@gibson.dropbear.id.au> wrote:
>
> > In fwd_scan_ports() we go through each of the automatic forwarding cases
> > (tcp, udp, inbound and outbound) in turn, scanning and calculating the
> > new forwarding map. However, to avoid avoid circular forwarding, some of
> > these maps affect each other. This has the odd effect that the ones
> > handled earlier are based on the previous scan of other maps, whereas
> > the later ones are based on the latest scan.
> >
> > That's not generally harmful, but it is counter-intuitive and results in a
> > few odd edge cases. Avoid this by performing all the scans first, without
> > regard to other maps, then applying the exclusions afterwards.
> >
> > One case has an extra wrinkle: for UDP we forwarded not just ports that
> > were listening on UDP but ones listening on TCP as well, for the benefit of
> > protocols like iperf3. We therefore also excluded listening ports from
> > both UDP and TCP from the other direction to avoid circular forwarding.
> >
> > This doesn't really make sense, though. To avoid circular forwarding, we
> > don't care *why* the other side is listening on UDP, just that it *is*
> > listening. I believe the explicit handling of the reverse TCP map was only
> > needed because the reverse map might have been one cycle out of date and
> > therefore not included a port opened because of the corresponding TCP port.
>
> Right, yes, that was the reason. I guess it makes sense to make this
> less hypothetical in the commit message if you re-spin. Same in 8/8.
There are some (trivial) conflicts with other things you've merged, so
I will respin. I've fixed this up.
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-10-31 2:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-11 4:48 [PATCH 0/8] RFC: Cleanups to auto port scanning David Gibson
2025-10-11 4:48 ` [PATCH 1/8] icmp: Remove vestiges of ICMP timer David Gibson
2025-10-11 4:48 ` [PATCH 2/8] tcp, udp, fwd: Run all port scanning from a single timer David Gibson
2025-10-11 4:48 ` [PATCH 3/8] fwd: Consolidate scans (not rebinds) in fwd.c David Gibson
2025-10-11 4:48 ` [PATCH 4/8] fwd: Move port exclusion handling from procfs_scan_listen() to callers David Gibson
2025-10-30 20:24 ` Stefano Brivio
2025-10-31 2:47 ` David Gibson
2025-10-31 8:21 ` Stefano Brivio
2025-11-03 1:43 ` David Gibson
2025-10-11 4:48 ` [PATCH 5/8] fwd: Share port scanning logic between init and timer cases David Gibson
2025-10-11 4:48 ` [PATCH 6/8] fwd: Check forwarding mode in fwd_scan_ports_*() rather than caller David Gibson
2025-10-11 4:48 ` [PATCH 7/8] fwd: Update all port maps before applying exclusions David Gibson
2025-10-30 20:24 ` Stefano Brivio
2025-10-31 2:51 ` David Gibson [this message]
2025-10-11 4:48 ` [PATCH 8/8] tcp, udp: Don't exclude ports in {tcp,udp}_port_rebind() David Gibson
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=aQQkOwgXuBIbgR0j@zatzit \
--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).