From: David Gibson <david@gibson.dropbear.id.au>
To: Jon Maloy <jmaloy@redhat.com>
Cc: sbrivio@redhat.com, dgibson@redhat.com, passt-dev@passt.top
Subject: Re: [PATCH v5 03/13] fwd: Unify guest accessibility checks with unified address array
Date: Mon, 2 Mar 2026 21:33:16 +1100 [thread overview]
Message-ID: <aaVnbG9wN6Hrhuyl@zatzit> (raw)
In-Reply-To: <20260222174445.743845-4-jmaloy@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 4645 bytes --]
On Sun, Feb 22, 2026 at 12:44:35PM -0500, Jon Maloy wrote:
> We replace the fwd_guest_accessible4() and fwd_guest_accessible6()
> functions with a unified fwd_guest_accessible() function that handles
> both address families. With the unified address array, we can check
> all configured addresses in a single pass using for_each_addr() with
> family filter INADDR_UNSPEC (== 0).
>
> Signed-off-by: Jon Maloy <jmaloy@redhat.com>
> ---
> fwd.c | 70 +++++++++++++++--------------------------------------------
> 1 file changed, 18 insertions(+), 52 deletions(-)
>
> diff --git a/fwd.c b/fwd.c
> index cf13ddd..edf6a6b 100644
> --- a/fwd.c
> +++ b/fwd.c
> @@ -880,19 +880,19 @@ static bool is_dns_flow(uint8_t proto, const struct flowside *ini)
> }
>
> /**
> - * fwd_guest_accessible4() - Is IPv4 address guest-accessible
> + * fwd_guest_accessible() - Is address guest-accessible
> * @c: Execution context
> - * @addr: Host visible IPv4 address
> + * @addr: Host visible address (IPv4 or IPv6)
> *
> * Return: true if @addr on the host is accessible to the guest without
> * translation, false otherwise
> */
> -static bool fwd_guest_accessible4(const struct ctx *c,
> - const struct in_addr *addr)
> +static bool fwd_guest_accessible(const struct ctx *c,
> + const union inany_addr *addr)
> {
> - struct inany_addr_entry *e = first_v4(c);
> + const struct inany_addr_entry *e;
>
> - if (IN4_IS_ADDR_LOOPBACK(addr))
> + if (inany_is_loopback(addr))
> return false;
>
> /* In socket interfaces 0.0.0.0 generally means "any" or unspecified,
> @@ -900,66 +900,32 @@ static bool fwd_guest_accessible4(const struct ctx *c,
> * that has a different meaning for host and guest, we can't let it
> * through untranslated.
> */
> - if (IN4_IS_ADDR_UNSPECIFIED(addr))
> - return false;
> -
> - /* For IPv4, addr_seen is initialised to addr, so is always a valid
> - * address
> - */
> - if ((e && IN4_ARE_ADDR_EQUAL(addr, inany_v4(&e->addr))) ||
> - IN4_ARE_ADDR_EQUAL(addr, &c->ip4.addr_seen))
> + if (inany_is_unspecified4(addr))
You want inany_is_unspecified(), not inany_is_unspecified4().
> return false;
>
> - return true;
> -}
> -
> -/**
> - * fwd_guest_accessible6() - Is IPv6 address guest-accessible
> - * @c: Execution context
> - * @addr: Host visible IPv6 address
> - *
> - * Return: true if @addr on the host is accessible to the guest without
> - * translation, false otherwise
> - */
> -static bool fwd_guest_accessible6(const struct ctx *c,
> - const struct in6_addr *addr)
> -{
> - if (IN6_IS_ADDR_LOOPBACK(addr))
> - return false;
> + /* Check against all configured guest addresses */
> + for_each_addr(e, c, 0)
> + if (inany_equals(addr, &e->addr))
> + return false;
>
> - if (first_v6(c) && IN6_ARE_ADDR_EQUAL(addr, &first_v6(c)->addr.a6))
> + /* Also check addr_seen: it tracks the address the guest is actually
> + * using, which may differ from configured addresses.
> + */
> + if (inany_equals4(addr, &c->ip4.addr_seen))
> 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
> * if it has been set to a real address.
> */
> - if (!IN6_IS_ADDR_UNSPECIFIED(&c->ip6.addr_seen) &&
> - IN6_ARE_ADDR_EQUAL(addr, &c->ip6.addr_seen))
> + if (!inany_v4(addr) &&
You don't need this test. If addr is IPv4, it necessarily won't equal
ip6.addr_seen which is IPv6.
> + !IN6_IS_ADDR_UNSPECIFIED(&c->ip6.addr_seen) &&
> + inany_equals6(addr, &c->ip6.addr_seen))
> return false;
>
> return true;
> }
>
> -/**
> - * fwd_guest_accessible() - Is IPv[46] address guest-accessible
> - * @c: Execution context
> - * @addr: Host visible IPv[46] address
> - *
> - * Return: true if @addr on the host is accessible to the guest without
> - * translation, false otherwise
> - */
> -static bool fwd_guest_accessible(const struct ctx *c,
> - const union inany_addr *addr)
> -{
> - const struct in_addr *a4 = inany_v4(addr);
> -
> - if (a4)
> - return fwd_guest_accessible4(c, a4);
> -
> - return fwd_guest_accessible6(c, &addr->a6);
> -}
> -
> /**
> * nat_outbound() - Apply address translation for outbound (TAP to HOST)
> * @c: Execution context
> --
> 2.52.0
>
--
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:[~2026-03-02 10:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-22 17:44 [PATCH v5 00/13] Introduce multiple addresses and late binding Jon Maloy
2026-02-22 17:44 ` [PATCH v5 01/13] ip: Introduce unified multi-address data structures Jon Maloy
2026-03-02 10:22 ` David Gibson
2026-02-22 17:44 ` [PATCH v5 02/13] ip: Introduce for_each_addr() macro for address iteration Jon Maloy
2026-03-02 10:29 ` David Gibson
2026-02-22 17:44 ` [PATCH v5 03/13] fwd: Unify guest accessibility checks with unified address array Jon Maloy
2026-03-02 10:33 ` David Gibson [this message]
2026-02-22 17:44 ` [PATCH v5 04/13] arp: Check all configured addresses in ARP filtering Jon Maloy
2026-03-02 10:41 ` David Gibson
2026-02-22 17:44 ` [PATCH v5 05/13] netlink: Return prefix length for IPv6 addresses in nl_addr_get() Jon Maloy
2026-03-02 10:43 ` David Gibson
2026-02-22 17:44 ` [PATCH v5 06/13] conf: Allow multiple -a/--address options per address family Jon Maloy
2026-03-02 10:51 ` David Gibson
2026-02-22 17:44 ` [PATCH v5 07/13] ip: Track observed guest IPv4 addresses in unified address array Jon Maloy
2026-03-03 1:40 ` David Gibson
2026-02-22 17:44 ` [PATCH v5 08/13] ip: Track observed guest IPv6 " Jon Maloy
2026-03-03 1:52 ` David Gibson
2026-02-22 17:44 ` [PATCH v5 09/13] migrate: Rename v1 address functions to v2 for clarity Jon Maloy
2026-03-03 1:53 ` David Gibson
2026-03-03 19:11 ` Stefano Brivio
2026-03-03 22:17 ` David Gibson
2026-03-03 22:56 ` David Gibson
2026-02-22 17:44 ` [PATCH v5 10/13] migrate: Update protocol to v3 for multi-address support Jon Maloy
2026-03-03 4:53 ` David Gibson
2026-02-22 17:44 ` [PATCH v5 11/13] dhcp, dhcpv6: Select addresses for DHCP distribution Jon Maloy
2026-03-03 5:26 ` David Gibson
2026-02-22 17:44 ` [PATCH v5 12/13] ndp: Support advertising multiple prefixes in Router Advertisement Jon Maloy
2026-02-22 17:44 ` [PATCH v5 13/13] netlink: Add host-side monitoring for late template interface binding Jon Maloy
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=aaVnbG9wN6Hrhuyl@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=dgibson@redhat.com \
--cc=jmaloy@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).