From: Jon Maloy <jmaloy@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: sbrivio@redhat.com, dgibson@redhat.com, passt-dev@passt.top
Subject: Re: [PATCH v3 04/11] fwd: Check all configured addresses in guest accessibility functions
Date: Wed, 4 Feb 2026 20:01:45 -0500 [thread overview]
Message-ID: <2b453804-9ba9-4ec6-9ad3-2dda13ef3df7@redhat.com> (raw)
In-Reply-To: <aYNGkHClfQv2yPQU@zatzit>
On 2026-02-04 08:16, David Gibson wrote:
> On Fri, Jan 30, 2026 at 04:44:40PM -0500, Jon Maloy wrote:
>> As a preparation for handling multiple addresses, we update
>> fwd_guest_accessible4() and fwd_guest_accessible6() to check
>> against all addresses in the unified addrs[] array using the
>> for_each_addr() macro.
>>
>> This ensures that when multiple addresses are configured via -a options,
>> inbound traffic for any of them is correctly detected as having no valid
>> forwarding path, and subsequently dropped. This occurs when a peer
>> address collides with an address the guest is using, and we have no
>> translation for it.
>>
>> Signed-off-by: Jon Maloy <jmaloy@redhat.com>
>>
>> ---
>> v2: Updated commit log to make it clearer
>> v3: Adapted to changes earlier in the series
>> ---
>> fwd.c | 25 +++++++++++++++++--------
>> 1 file changed, 17 insertions(+), 8 deletions(-)
>>
>> diff --git a/fwd.c b/fwd.c
>> index 54248a3..20d581d 100644
>> --- a/fwd.c
>> +++ b/fwd.c
>> @@ -502,6 +502,8 @@ static bool is_dns_flow(uint8_t proto, const struct flowside *ini)
>> static bool fwd_guest_accessible4(const struct ctx *c,
>> const struct in_addr *addr)
>
> With the changes to this point, there's no longer a point to having
> separate fwd_guest_accessible4() and fwd_guest_accessible6()
> functions. fwd_guest_accessible() can check against the combined list
> in a single pass.
Absolutely. I have already identified several functions which can be
unified in a similar way, and have already implemented some.
But I still want to wait with such changes until this series has been
applied.
///jon
>
> This is an example of the simplfications that I think will outweigh
> the complications introduced by using merged list for v4 and v6
> addresses.
>
>> {
>> + const struct inany_addr_entry *e;
>> +
>> if (IN4_IS_ADDR_LOOPBACK(addr))
>> return false;
>>
>> @@ -513,12 +515,15 @@ static bool fwd_guest_accessible4(const struct ctx *c,
>> if (IN4_IS_ADDR_UNSPECIFIED(addr))
>> return false;
>>
>> - /* For IPv4, addr_seen is initialised to addr, so is always a valid
>> - * address
>> + /* Check against all configured guest addresses */
>> + for_each_addr(c, e, AF_INET)
>> + if (IN4_ARE_ADDR_EQUAL(addr, inany_v4(&e->addr)))
>> + return false;
>> +
>> + /* Also check addr_seen: it tracks the address the guest is actually
>> + * using, which may differ from configured addresses.
>> */
>> - if ((first_v4(c) &&
>> - IN4_ARE_ADDR_EQUAL(addr, inany_v4(&first_v4(c)->addr))) ||
>> - IN4_ARE_ADDR_EQUAL(addr, &c->ip4.addr_seen))
>> + if (IN4_ARE_ADDR_EQUAL(addr, &c->ip4.addr_seen))
>> return false;
>>
>> return true;
>> @@ -535,11 +540,15 @@ static bool fwd_guest_accessible4(const struct ctx *c,
>> static bool fwd_guest_accessible6(const struct ctx *c,
>> const struct in6_addr *addr)
>> {
>> + const struct inany_addr_entry *e;
>> +
>> if (IN6_IS_ADDR_LOOPBACK(addr))
>> return false;
>>
>> - if (first_v6(c) && IN6_ARE_ADDR_EQUAL(addr, &first_v6(c)->addr.a6))
>> - return false;
>> + /* Check against all configured guest addresses */
>> + for_each_addr(c, e, AF_INET6)
>> + if (IN6_ARE_ADDR_EQUAL(addr, &e->addr.a6))
>> + return false;
>>
>> /* For IPv6, addr_seen starts unspecified, because we don't know what LL
>> * address the guest will take until we see it. Only check against it
>> @@ -714,7 +723,7 @@ bool nat_inbound(const struct ctx *c, const union inany_addr *addr,
>> first_v4(c) && inany_equals(addr, &first_v4(c)->addr)) {
>> *translated = inany_from_v4(c->ip4.map_guest_addr);
>> } else if (!IN6_IS_ADDR_UNSPECIFIED(&c->ip6.map_guest_addr) &&
>> - first_v6(c) && inany_equals6(addr, &first_v6(c)->addr.a6)) {
>> + first_v6(c) && inany_equals(addr, &first_v6(c)->addr)) {
>> translated->a6 = c->ip6.map_guest_addr;
>> } else if (fwd_guest_accessible(c, addr)) {
>> *translated = *addr;
>> --
>> 2.52.0
>>
>
next prev parent reply other threads:[~2026-02-05 1:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 21:44 [PATCH v3 00/11] Introduce multiple addresses Jon Maloy
2026-01-30 21:44 ` [PATCH v3 01/11] conf: Support CIDR notation for -a/--address option Jon Maloy
2026-02-04 12:50 ` David Gibson
2026-02-05 0:56 ` Jon Maloy
2026-02-06 3:26 ` David Gibson
2026-01-30 21:44 ` [PATCH v3 02/11] ip: Add IN4_MASK() macro for IPv4 netmask calculation Jon Maloy
2026-02-04 12:52 ` David Gibson
2026-01-30 21:44 ` [PATCH v3 03/11] ip: Introduce unified multi-address data structures Jon Maloy
2026-02-06 8:24 ` David Gibson
2026-01-30 21:44 ` [PATCH v3 04/11] fwd: Check all configured addresses in guest accessibility functions Jon Maloy
2026-02-04 13:16 ` David Gibson
2026-02-05 1:01 ` Jon Maloy [this message]
2026-02-06 3:29 ` David Gibson
2026-01-30 21:44 ` [PATCH v3 05/11] arp: Check all configured addresses in ARP filtering Jon Maloy
2026-02-06 8:34 ` David Gibson
2026-01-30 21:44 ` [PATCH v3 06/11] pasta: Extract pasta_ns_conf_ip4/6() to reduce nesting Jon Maloy
2026-02-06 8:40 ` David Gibson
2026-01-30 21:44 ` [PATCH v3 07/11] conf: Allow multiple -a/--address options per address family Jon Maloy
2026-02-06 8:47 ` David Gibson
2026-01-30 21:44 ` [PATCH v3 08/11] migrate: Rename v1 address functions to v2 for clarity Jon Maloy
2026-02-06 8:50 ` David Gibson
2026-01-30 21:44 ` [PATCH v3 09/11] ip: Track observed guest IPv4 addresses in unified address array Jon Maloy
2026-02-09 22:17 ` David Gibson
2026-01-30 21:44 ` [PATCH v3 10/11] ip: Track observed guest IPv6 " Jon Maloy
2026-02-09 22:30 ` David Gibson
2026-01-30 21:44 ` [PATCH v3 11/11] conf: Select addresses for DHCP and NDP distribution Jon Maloy
2026-02-09 22:46 ` 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=2b453804-9ba9-4ec6-9ad3-2dda13ef3df7@redhat.com \
--to=jmaloy@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=dgibson@redhat.com \
--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).