public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: passt-dev@passt.top, Jon Maloy <jmaloy@redhat.com>,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH v6 06/18] pif: Limit pif names to 128 bytes
Date: Tue, 05 May 2026 01:10:35 +0200 (CEST)	[thread overview]
Message-ID: <20260505011035.6915f9ec@elisabeth> (raw)
In-Reply-To: <0834495e-1818-406a-8737-c8e48a4cea6d@redhat.com>

On Mon, 4 May 2026 11:12:16 +0200
Laurent Vivier <lvivier@redhat.com> wrote:

> On 5/3/26 23:55, Stefano Brivio wrote:
> > From: David Gibson <david@gibson.dropbear.id.au>
> > 
> > All current pif names are quite short, and we expect them to remain short
> > when/if we allow arbitrary pifs.  However, because of the structure of
> > the current code we don't enforce any limit on the length.
> > 
> > This will become more important with dynamic configuration updates, so
> > start enforcing a length limit.  Specifically we allow pif names to be up
> > to 128 bytes (PIF_NAME_SIZE), including the terminating \0.  This is
> > more or less arbitrary, but seems like it should be comfortably enough for
> > all the cases we have in mind.
> > 
> > Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> > Signed-off-by: Stefano Brivio <sbrivio@redhat.com>  
> 
> Reviewed-by: Laurent Vivier <lvivier@redhat.com>
> 
> There is a little typo below
> 
> > ---
> >   pif.c | 2 +-
> >   pif.h | 5 ++++-
> >   2 files changed, 5 insertions(+), 2 deletions(-)
> > 
> > diff --git a/pif.c b/pif.c
> > index 1e80724..d5e3161 100644
> > --- a/pif.c
> > +++ b/pif.c
> > @@ -17,7 +17,7 @@
> >   #include "inany.h"
> >   #include "epoll_ctl.h"
> >   
> > -const char *pif_type_str[] = {
> > +const char pif_type_str[][PIF_NAME_SIZE] = {
> >   	[PIF_NONE]		= "<none>",
> >   	[PIF_HOST]		= "HOST",
> >   	[PIF_TAP]		= "TAP",
> > diff --git a/pif.h b/pif.h
> > index 7bb58e5..90dd3a3 100644
> > --- a/pif.h
> > +++ b/pif.h
> > @@ -35,7 +35,9 @@ enum pif_type {
> >   	PIF_NUM_TYPES,
> >   };
> >   
> > -extern const char *pif_type_str[];
> > +/* Maxmimum size of a pif name, including \0 */  
> 
> "Maximum"

Fixed in v7.

-- 
Stefano


  reply	other threads:[~2026-05-04 23:10 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-03 21:55 [PATCH v6 00/18] Dynamic configuration update implementation Stefano Brivio
2026-05-03 21:55 ` [PATCH v6 01/18] conf, fwd: Stricter rule checking in fwd_rule_add() Stefano Brivio
2026-05-04  8:38   ` Laurent Vivier
2026-05-03 21:55 ` [PATCH v6 02/18] fwd_rule: Move ephemeral port probing to fwd_rule.c Stefano Brivio
2026-05-03 21:55 ` [PATCH v6 03/18] fwd, conf: Move rule parsing code to fwd_rule.[ch] Stefano Brivio
2026-05-03 21:55 ` [PATCH v6 04/18] fwd_rule: Move conflict checking back within fwd_rule_add() Stefano Brivio
2026-05-03 21:55 ` [PATCH v6 05/18] fwd: Generalise fwd_rules_info() Stefano Brivio
2026-05-03 21:55 ` [PATCH v6 06/18] pif: Limit pif names to 128 bytes Stefano Brivio
2026-05-04  9:12   ` Laurent Vivier
2026-05-04 23:10     ` Stefano Brivio [this message]
2026-05-03 21:55 ` [PATCH v6 07/18] fwd_rule: Fix some format specifiers Stefano Brivio
2026-05-04  9:59   ` Laurent Vivier
2026-05-03 21:55 ` [PATCH v6 08/18] pesto: Introduce stub configuration tool Stefano Brivio
2026-05-04 10:51   ` Laurent Vivier
2026-05-04 23:10     ` Stefano Brivio
2026-05-03 21:55 ` [PATCH v6 09/18] pesto, log: Share log.h (but not log.c) with pesto tool Stefano Brivio
2026-05-04  9:49   ` Laurent Vivier
2026-05-04 23:11     ` Stefano Brivio
2026-05-03 21:55 ` [PATCH v6 10/18] pesto, conf: Have pesto connect to passt and check versions Stefano Brivio
2026-05-04 12:01   ` Laurent Vivier
2026-05-04 12:13     ` Laurent Vivier
2026-05-03 21:55 ` [PATCH v6 11/18] pesto: Expose list of pifs to pesto and optionally display Stefano Brivio
2026-05-04 14:34   ` Laurent Vivier
2026-05-04 23:10     ` Stefano Brivio
2026-05-03 21:55 ` [PATCH v6 12/18] ip: Prepare ip.[ch] for sharing with pesto tool Stefano Brivio
2026-05-04 14:52   ` Laurent Vivier
2026-05-04 23:10     ` Stefano Brivio
2026-05-03 21:55 ` [PATCH v6 13/18] inany: Prepare inany.[ch] " Stefano Brivio
2026-05-04 15:37   ` Laurent Vivier
2026-05-03 21:55 ` [PATCH v6 14/18] pesto: Read current ruleset from passt/pasta and optionally display it Stefano Brivio
2026-05-04 16:10   ` Laurent Vivier
2026-05-04 23:11     ` Stefano Brivio
2026-05-03 21:55 ` [PATCH v6 15/18] pesto: Parse and add new rules from command line Stefano Brivio
2026-05-04 16:44   ` Laurent Vivier
2026-05-04 23:11     ` Stefano Brivio
2026-05-04 23:18       ` Stefano Brivio
2026-05-03 21:55 ` [PATCH v6 16/18] pesto, conf: Send updated rules from pesto back to passt/pasta Stefano Brivio
2026-05-03 21:56 ` [PATCH v6 17/18] conf, fwd: Allow switching to new rules received from pesto Stefano Brivio
2026-05-03 21:56 ` [PATCH v6 18/18] fwd_rule: Fix static checkers warnings in fwd_rule_add() 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=20260505011035.6915f9ec@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=jmaloy@redhat.com \
    --cc=lvivier@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).