From: Jon Maloy <jmaloy@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>,
passt-dev@passt.top, Stefano Brivio <sbrivio@redhat.com>
Subject: Re: [PATCH v4 06/17] pif: Limit pif names to 128 bytes
Date: Sat, 25 Apr 2026 21:03:09 [thread overview]
Message-ID: <8fe5123e-2594-48cd-a94e-62f4c03a4dab@redhat.com> (raw)
In-Reply-To: <20260421044217.2500314-7-david@gibson.dropbear.id.au>
On 2026-04-21 00:42, David Gibson wrote:
> 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>
Reviewed-by: Jon Maloy <jmaloy@redhat.com>
If you fix a typo below.
> ---
> pif.c | 2 +-
> pif.h | 5 ++++-
> 2 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/pif.c b/pif.c
> index 1e807247..d5e31613 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 7bb58e5c..90dd3a32 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 */
s/Maxmimum/Maximum/g
> +#define PIF_NAME_SIZE (128)
> +extern const char pif_type_str[][PIF_NAME_SIZE];
>
> static inline const char *pif_type(enum pif_type pt)
> {
> @@ -43,6 +45,7 @@ static inline const char *pif_type(enum pif_type pt)
> return pif_type_str[pt];
> else
> return "?";
> + static_assert(sizeof("?") <= PIF_NAME_SIZE);
> }
>
> static inline const char *pif_name(uint8_t pif)
next prev parent reply other threads:[~2026-04-25 21:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 4:42 [PATCH v4 00/17] RFC: Dynamic configuration update implementation David Gibson
2026-04-21 4:42 ` [PATCH v4 01/17] conf, fwd: Stricter rule checking in fwd_rule_add() David Gibson
2026-04-21 4:42 ` [PATCH v4 02/17] fwd_rule: Move ephemeral port probing to fwd_rule.c David Gibson
2026-04-21 4:42 ` [PATCH v4 03/17] fwd, conf: Move rule parsing code to fwd_rule.[ch] David Gibson
2026-04-21 4:42 ` [PATCH v4 04/17] fwd_rule: Move conflict checking back within fwd_rule_add() David Gibson
2026-04-21 4:42 ` [PATCH v4 05/17] fwd: Generalise fwd_rules_info() David Gibson
2026-04-21 4:42 ` [PATCH v4 06/17] pif: Limit pif names to 128 bytes David Gibson
2026-04-25 19:03 ` Jon Maloy [this message]
2026-04-21 4:42 ` [PATCH v4 07/17] fwd_rule: Fix some format specifiers David Gibson
2026-04-21 4:42 ` [PATCH v4 08/17] pesto: Introduce stub configuration tool David Gibson
2026-04-21 4:42 ` [PATCH v4 09/17] pesto, log: Share log.h (but not log.c) with pesto tool David Gibson
2026-04-21 4:42 ` [PATCH v4 10/17] pesto, conf: Have pesto connect to passt and check versions David Gibson
2026-04-21 4:42 ` [PATCH v4 11/17] pesto: Expose list of pifs to pesto and optionally display David Gibson
2026-04-21 4:42 ` [PATCH v4 12/17] ip: Prepare ip.[ch] for sharing with pesto tool David Gibson
2026-04-21 4:42 ` [PATCH v4 13/17] inany: Prepare inany.[ch] " David Gibson
2026-04-21 4:42 ` [PATCH v4 14/17] pesto: Read current ruleset from passt/pasta and optionally display it David Gibson
2026-04-21 4:42 ` [PATCH v4 15/17] pesto: Parse and add new rules from command line David Gibson
2026-04-21 4:42 ` [PATCH v4 16/17] pesto, conf: Send updated rules from pesto back to passt/pasta David Gibson
2026-04-21 4:42 ` [PATCH v4 17/17] conf, fwd: Allow switching to new rules received from pesto David Gibson
2026-04-21 6:26 ` [PATCH v4 00/17] IGNORE RFC: Dynamic configuration update implementation 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=8fe5123e-2594-48cd-a94e-62f4c03a4dab@redhat.com \
--to=jmaloy@redhat.com \
--cc=david@gibson.dropbear.id.au \
--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).