From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>, passt-dev@passt.top
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH 2/3] tcp: Always populate oaddr field for socket initiated flows
Date: Thu, 20 Nov 2025 15:34:52 +1100 [thread overview]
Message-ID: <20251120043453.108919-3-david@gibson.dropbear.id.au> (raw)
In-Reply-To: <20251120043453.108919-1-david@gibson.dropbear.id.au>
When we receive a TCP connection, we get the peer address from the accept()
call. In the case of a listening socket with an unspecified address (:: or
0.0.0.0) the local address of the accept()ed socket could vary. We don't
get that from the accept() - we must explicitly call getsockname() to get
it.
Currently we avoid the latency of that extra syscall, and therefore don't
populate the initiating 'oaddr' field of a flow created by an incoming TCP
socket connection. This more or less works, because we rarely need that
local address, but it does cause some oddities:
* For migration we need the local address to recreate the socket on the
destination, so we *do* call getsockname() in vhost-user mode
* It limits our options in terms of forwarding connections flexibly based
on the address to which they're received
* It differs from UDP, where we explicitly use the IP_PKTINFO cmsg to
populate oaddr.
* It means (some) flow debug messages will contain wildcards instead of
real local addresses
In theory we can elide this call when accept()ing from a socket bound to
a specific address instead of a wildcard. However to do that will need
revisions to the data structures we use to keep track of listening sockets.
The lack of this information is making it hard to implement some fixes we
want. So, pay the price of the extra syscall to get this information, with
the hope that we can later optimise it away for some cases.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
---
tcp.c | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/tcp.c b/tcp.c
index bd25952f..e734a957 100644
--- a/tcp.c
+++ b/tcp.c
@@ -2354,11 +2354,9 @@ void tcp_listen_handler(const struct ctx *c, union epoll_ref ref,
ini = flow_initiate_sa(flow, ref.tcp_listen.pif, &sa,
NULL, ref.tcp_listen.port);
- if (c->mode == MODE_VU) { /* Rebind to same address after migration */
- if (getsockname(s, &sa.sa, &sl) ||
- inany_from_sockaddr(&ini->oaddr, &ini->oport, &sa) < 0)
- err_perror("Can't get local address for socket %i", s);
- }
+ if (getsockname(s, &sa.sa, &sl) ||
+ inany_from_sockaddr(&ini->oaddr, &ini->oport, &sa) < 0)
+ err_perror("Can't get local address for socket %i", s);
if (!inany_is_unicast(&ini->eaddr) || ini->eport == 0) {
char sastr[SOCKADDR_STRLEN];
--
2.51.1
next prev parent reply other threads:[~2025-11-20 4:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 4:34 [PATCH 0/3] Fix bug 113 David Gibson
2025-11-20 4:34 ` [PATCH 1/3] util: Rename sock_l4_dualstack() to sock_l4_dualstack_any() David Gibson
2025-11-20 4:34 ` David Gibson [this message]
2025-11-20 4:34 ` [PATCH 3/3] fwd: Preserve non-standard loopback address when splice forwarding 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=20251120043453.108919-3-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).