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 v2 1/9] conf: Support CIDR notation for -a/--address option
Date: Tue, 27 Jan 2026 19:42:21 +1100 [thread overview]
Message-ID: <aXh6baMgZsn6gz53@zatzit> (raw)
In-Reply-To: <8ac549ba-c893-4e68-ac1c-72974781fa4e@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2341 bytes --]
On Wed, Jan 21, 2026 at 07:06:10PM -0500, Jon Maloy wrote:
> On 2026-01-19 00:02, David Gibson wrote:
> > On Sun, Jan 18, 2026 at 05:16:04PM -0500, Jon Maloy wrote:
[snip]
> > > +/**
> > > + * conf_addr_prefix_len() - Parse address with optional prefix length
> > > + * @arg: Address string, optionally with /prefix_len suffix (modified)
> > > + * @addr: Output for parsed address
> > > + * @prefix_len: Output for prefix length (0 if not specified)
> > > + *
> > > + * Return: AF_INET for IPv4, AF_INET6 for IPv6, -1 on error
> > > + */
> > > +static int conf_addr_prefix_len(char *arg, union inany_addr *addr,
> > > + int *prefix_len)
> > > +{
> > > + char *slash;
> > > +
> > > + *prefix_len = 0;
> > > +
> > > + /* Check for /prefix_len suffix */
> > > + slash = strchr(arg, '/');
> > > + if (slash) {
> > > + unsigned long len;
> > > + char *end;
> > > +
> > > + *slash = '\0';
> > > + errno = 0;
> > > + len = strtoul(slash + 1, &end, 10);
> > > + if (errno || *end)
> > > + return -1;
> > > +
> > > + *prefix_len = len;
> > > + }
> > > +
> > > + if (!inany_prefix_pton(arg, addr, prefix_len))
> > > + return -1;
> >
> > Oh, sorry, I wasn't clear. My idea was that inany_prefix_pton() would
> > handle the parsing (strchr(), strtoul() etc.) of the prefix length
> > internally, rather than doing that here then adjusting it in there.
>
> Ok. So I basically eliminate conf_addr_perfix_len() and replace it with
> a inany_prefix_pton() which does all the job. Makes sense.
Yes.
> Regarding the prefix length adjustment: if I give some address in one of the
> following two formats:
> 192.168.1.1/24
> or
> ::ffff:192.168.1.1/120
>
> they will both be stored in the array in exactly the same
> format, as ::ffff:192.168.1.1.
Yes.
> It makes little sense to use two different prefix lengths just
> because the user happened to use some specific format, and would
> only create problems for anybody trying to access that entry later.
> I think this one *should* be adjusted.
Absolutely, but they should all be adjusted to the IPv6 form, not the
IPv4 form.
--
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-01-27 8:46 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 [this message]
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
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=aXh6baMgZsn6gz53@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).