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 1/3] Revert "fwd: Update all port maps before applying exclusions"
Date: Wed, 19 Nov 2025 15:26:32 +1100 [thread overview]
Message-ID: <20251119042634.2978171-2-david@gibson.dropbear.id.au> (raw)
In-Reply-To: <20251119042634.2978171-1-david@gibson.dropbear.id.au>
This reverts commit 81942a2417357ff10b02ccc8275cde2d4d6fbfbe.
That commit was based on the premise of trying to make all the exclusions
use the "latest" scan data. That was a fundamentally wrong approach: what
we need to exclude is listening ports that pasta itself has created. That
is, we need to exclude ports that we were _already_ listening on, not ones
that we intend to listen once we rebind - we *want* the old data.
Reverting this reduces the cases in which bug 176 occurs, but it's not a
complete fix.
Link: https://bugs.passt.top/show_bug.cgi?id=176
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
---
fwd.c | 47 +++++++++++++++++++++++------------------------
1 file changed, 23 insertions(+), 24 deletions(-)
diff --git a/fwd.c b/fwd.c
index 68bb1166..7b6c40fb 100644
--- a/fwd.c
+++ b/fwd.c
@@ -358,8 +358,10 @@ static void procfs_scan_listen(int fd, unsigned int lstate, uint8_t *map)
/**
* fwd_scan_ports_tcp() - Scan /proc to update TCP forwarding map
* @fwd: Forwarding information to update
+ * @rev: Forwarding information for the reverse direction
*/
-static void fwd_scan_ports_tcp(struct fwd_ports *fwd)
+static void fwd_scan_ports_tcp(struct fwd_ports *fwd,
+ const struct fwd_ports *rev)
{
if (fwd->mode != FWD_AUTO)
return;
@@ -367,15 +369,20 @@ static void fwd_scan_ports_tcp(struct fwd_ports *fwd)
memset(fwd->map, 0, PORT_BITMAP_SIZE);
procfs_scan_listen(fwd->scan4, TCP_LISTEN, fwd->map);
procfs_scan_listen(fwd->scan6, TCP_LISTEN, fwd->map);
+ bitmap_and_not(fwd->map, PORT_BITMAP_SIZE, fwd->map, rev->map);
}
/**
* fwd_scan_ports_udp() - Scan /proc to update UDP forwarding map
* @fwd: Forwarding information to update
+ * @rev: Forwarding information for the reverse direction
* @tcp_fwd: Corresponding TCP forwarding information
+ * @tcp_rev: TCP forwarding information for the reverse direction
*/
static void fwd_scan_ports_udp(struct fwd_ports *fwd,
- const struct fwd_ports *tcp_fwd)
+ const struct fwd_ports *rev,
+ const struct fwd_ports *tcp_fwd,
+ const struct fwd_ports *tcp_rev)
{
if (fwd->mode != FWD_AUTO)
return;
@@ -391,6 +398,14 @@ static void fwd_scan_ports_udp(struct fwd_ports *fwd,
*/
procfs_scan_listen(tcp_fwd->scan4, TCP_LISTEN, fwd->map);
procfs_scan_listen(tcp_fwd->scan6, TCP_LISTEN, fwd->map);
+
+ /* This means we need to skip numbers of TCP ports bound on the other
+ * side, too. Otherwise, we would detect corresponding UDP ports as
+ * bound and try to forward them from the opposite side, but it's
+ * already us handling them.
+ */
+ bitmap_and_not(fwd->map, PORT_BITMAP_SIZE, fwd->map, rev->map);
+ bitmap_and_not(fwd->map, PORT_BITMAP_SIZE, fwd->map, tcp_rev->map);
}
/**
@@ -399,28 +414,12 @@ static void fwd_scan_ports_udp(struct fwd_ports *fwd,
*/
static void fwd_scan_ports(struct ctx *c)
{
- fwd_scan_ports_tcp(&c->tcp.fwd_out);
- fwd_scan_ports_tcp(&c->tcp.fwd_in);
- fwd_scan_ports_udp(&c->udp.fwd_out, &c->tcp.fwd_out);
- fwd_scan_ports_udp(&c->udp.fwd_in, &c->tcp.fwd_in);
-
- if (c->tcp.fwd_out.mode == FWD_AUTO) {
- bitmap_and_not(c->tcp.fwd_out.map, PORT_BITMAP_SIZE,
- c->tcp.fwd_out.map, c->tcp.fwd_in.map);
- }
- if (c->tcp.fwd_in.mode == FWD_AUTO) {
- bitmap_and_not(c->tcp.fwd_in.map, PORT_BITMAP_SIZE,
- c->tcp.fwd_in.map, c->tcp.fwd_out.map);
- }
-
- if (c->udp.fwd_out.mode == FWD_AUTO) {
- bitmap_and_not(c->udp.fwd_out.map, PORT_BITMAP_SIZE,
- c->udp.fwd_out.map, c->udp.fwd_in.map);
- }
- if (c->udp.fwd_in.mode == FWD_AUTO) {
- bitmap_and_not(c->udp.fwd_in.map, PORT_BITMAP_SIZE,
- c->udp.fwd_in.map, c->udp.fwd_out.map);
- }
+ fwd_scan_ports_tcp(&c->tcp.fwd_out, &c->tcp.fwd_in);
+ fwd_scan_ports_tcp(&c->tcp.fwd_in, &c->tcp.fwd_out);
+ fwd_scan_ports_udp(&c->udp.fwd_out, &c->udp.fwd_in,
+ &c->tcp.fwd_out, &c->tcp.fwd_in);
+ fwd_scan_ports_udp(&c->udp.fwd_in, &c->udp.fwd_out,
+ &c->tcp.fwd_in, &c->tcp.fwd_out);
}
/**
--
2.51.1
next prev parent 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 [PATCH 0/3] Fix regression in auto port forwarding David Gibson
2025-11-19 4:26 ` David Gibson [this message]
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-2-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).