public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: passt-dev@passt.top, Stefano Brivio <sbrivio@redhat.com>
Subject: Re: [PATCH v3 0/8] Reduce differences between inbound and outbound socket binding
Date: Thu, 30 Oct 2025 14:58:58 +1100	[thread overview]
Message-ID: <aQLigkyUuJsZAP7X@zatzit> (raw)
In-Reply-To: <20251029062628.1647051-1-david@gibson.dropbear.id.au>

[-- Attachment #1: Type: text/plain, Size: 1806 bytes --]

On Wed, Oct 29, 2025 at 05:26:20PM +1100, David Gibson wrote:
> The fact that outbound forwarding sockets are bound to the loopback
> address, whereas inbound forwarding sockets are (by default) bound to
> the unspecified address leads to some unexpected differences between
> the paths setting up each of them.
> 
> An idea for tackling bug 100 suggested a different approach which will
> also reduce some of those differences and allow more code to be shared
> between the two paths.  I've since discovered that this approach may
> not help for bug 100, but it might still be worthwhile for the clean
> up.
> 
> Patches 1..6/8 are cleanups which shouldn't change behaviour, and I
> think are ready to merge.  7/8 is (arguably) a behavioural change, but
> I've made my case for it in the patch comment.  8/8 needs some further
> consideration, since I've discovered it does not fix bug 100 as is,
> I'm including it for advance review, though.

Follow up on 8/8 now I've looked into SO_BINDTODEVICE semantics more
clearly.  Unfortunately this approach won't work to fix bug 100 [0].
I still think the change is useful for the internals and it may also
help with some other bugs such as 113.

So, I don't think the code of 8/8 needs to change, but the comments
and commit message do.

Here's my plan:
 - I'll wait for review on this draft
 - If it needs a respin, I'll make those doc changes in the next
   version
 - If the series doesn't need a respin, go ahead and apply 1..7, and
   I'll send a revised 8/8 separately.

[0] https://bugs.passt.top/show_bug.cgi?id=100#c8

-- 
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 --]

      parent reply	other threads:[~2025-10-30  4:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29  6:26 David Gibson
2025-10-29  6:26 ` [PATCH v3 1/8] inany: Let length of sockaddr_inany be implicit from the family David Gibson
2025-11-13  6:33   ` Stefano Brivio
2025-11-13 22:53     ` David Gibson
2025-10-29  6:26 ` [PATCH v3 2/8] util, flow, pif: Simplify sock_l4_sa() interface David Gibson
2025-11-13  6:33   ` Stefano Brivio
2025-11-13 23:21     ` David Gibson
2025-11-18  0:19       ` Stefano Brivio
2025-11-18  3:34         ` David Gibson
2025-11-19 11:42           ` Stefano Brivio
2025-11-20  0:05             ` David Gibson
2025-11-20  2:22               ` David Gibson
2025-10-29  6:26 ` [PATCH v3 3/8] tcp: Merge tcp_ns_sock_init[46]() into tcp_sock_init_one() David Gibson
2025-10-29  6:26 ` [PATCH v3 4/8] udp: Unify some more inbound/outbound parts of udp_sock_init() David Gibson
2025-11-13  6:33   ` Stefano Brivio
2025-11-13 23:33     ` David Gibson
2025-10-29  6:26 ` [PATCH v3 5/8] udp: Move udp_sock_init() special case to its caller David Gibson
2025-10-29  6:26 ` [PATCH v3 6/8] util: Fix setting of IPV6_V6ONLY socket option David Gibson
2025-11-13  6:33   ` Stefano Brivio
2025-11-14  0:24     ` David Gibson
2025-11-18  0:19       ` Stefano Brivio
2025-10-29  6:26 ` [PATCH v3 7/8] tcp, udp: Remove fallback if creating dual stack socket fails David Gibson
2025-10-29  6:26 ` [PATCH v3 8/8] [RFC, DO NOT APPLY] tcp, udp: Bind outbound listening sockets by interface instead of address David Gibson
2025-10-30  3:58 ` David Gibson [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=aQLigkyUuJsZAP7X@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).