From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Jon Maloy <jmaloy@redhat.com>, dgibson@redhat.com, passt-dev@passt.top
Subject: Re: [PATCH v2 2/9] ip: Introduce unified multi-address data structures
Date: Tue, 27 Jan 2026 11:31:35 +0100 [thread overview]
Message-ID: <20260127113135.11855e17@elisabeth> (raw)
In-Reply-To: <aXh-atI1adlwuk4X@zatzit>
On Tue, 27 Jan 2026 19:59:22 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> On Wed, Jan 21, 2026 at 02:02:05PM +0100, Stefano Brivio wrote:
> > On Sun, 18 Jan 2026 17:16:05 -0500
> > Jon Maloy <jmaloy@redhat.com> wrote:
> [snip]
> > > +/* Flags for struct inany_addr_entry */
> > > +#define INANY_ADDR_CONFIGURED (1 << 0) /* User set via -a */
> > > +#define INANY_ADDR_HOST (1 << 1) /* From host interface */
> > > +
> > > +/**
> > > + * struct inany_addr_entry - Unified IPv4/IPv6 address entry
> > > + * @addr: IPv4 (as mapped) or IPv6 address
> > > + * @prefix_len: Prefix length (0-32 for IPv4, 0-128 for IPv6)
> >
> > This should be 1-32 and 1-128, unless you find a way to make /0
> > assignments working (see my comment on 1/9).
>
> Here in the data structure it should still be 0-N. We can't make use
> of a /0 for addresses, but we probably can for routes at some point
> later.
Ah, right, default routes... of course.
--
Stefano
next prev parent reply other threads:[~2026-01-27 10:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-18 22:16 [PATCH v2 0/9] Introduce multiple addresses Jon Maloy
2026-01-18 22:16 ` [PATCH v2 1/9] conf: Support CIDR notation for -a/--address option Jon Maloy
2026-01-19 5:02 ` David Gibson
2026-01-22 0:06 ` Jon Maloy
2026-01-27 8:42 ` David Gibson
2026-01-21 8:15 ` Stefano Brivio
2026-01-18 22:16 ` [PATCH v2 2/9] ip: Introduce unified multi-address data structures Jon Maloy
2026-01-19 7:22 ` David Gibson
2026-01-21 13:02 ` Stefano Brivio
2026-01-27 8:59 ` David Gibson
2026-01-27 10:31 ` Stefano Brivio [this message]
2026-01-18 22:16 ` [PATCH v2 3/9] conf: Refactor conf_print() for multi-address support Jon Maloy
2026-01-19 7:25 ` David Gibson
2026-01-21 13:02 ` Stefano Brivio
2026-01-27 9:07 ` David Gibson
2026-01-27 10:30 ` Stefano Brivio
2026-01-18 22:16 ` [PATCH v2 4/9] fwd: Check all configured addresses in guest accessibility functions Jon Maloy
2026-01-19 7:29 ` David Gibson
2026-01-18 22:16 ` [PATCH v2 5/9] arp: Check all configured addresses in ARP filtering Jon Maloy
2026-01-19 8:28 ` David Gibson
2026-01-18 22:16 ` [PATCH v2 6/9] conf: Allow multiple -a/--address options per address family Jon Maloy
2026-01-19 8:41 ` David Gibson
2026-01-21 19:42 ` Stefano Brivio
2026-01-18 22:16 ` [PATCH v2 7/9] pasta: Unify address configuration paths using address array Jon Maloy
2026-01-21 19:42 ` Stefano Brivio
2026-01-18 22:16 ` [PATCH v2 8/9] ip: Track observed guest IPv4 addresses in unified " Jon Maloy
2026-01-21 19:42 ` Stefano Brivio
2026-01-18 22:16 ` [PATCH v2 9/9] ip: Track observed guest IPv6 " Jon Maloy
2026-01-21 19:42 ` 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=20260127113135.11855e17@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=dgibson@redhat.com \
--cc=jmaloy@redhat.com \
--cc=passt-dev@passt.top \
/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).