public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: Jon Maloy <jmaloy@redhat.com>, passt-dev@passt.top
Subject: Re: [PATCH v5 01/18] conf, fwd: Stricter rule checking in fwd_rule_add()
Date: Mon, 4 May 2026 14:24:05 +1000	[thread overview]
Message-ID: <afgfZXGUWwAQ1WDm@zatzit> (raw)
In-Reply-To: <20260503235607.70fea978@elisabeth>

[-- Attachment #1: Type: text/plain, Size: 1901 bytes --]

On Sun, May 03, 2026 at 11:56:08PM +0200, Stefano Brivio wrote:
> On Sun, 26 Apr 2026 11:31:24 +1000
> David Gibson <david@gibson.dropbear.id.au> wrote:
> 
> > On Sat, Apr 25, 2026 at 11:31:40AM -0400, Jon Maloy wrote:
> > > 
> > > 
> > > On 2026-04-21 02:24, David Gibson wrote:  
> > > > Although fwd_rule_add() performs some sanity checks on the rule it is
> > > > given, there are invalid rules we don't check for, assuming that its
> > > > callers will do that.
> > > >   
> > >   
> > > > diff --git a/fwd.c b/fwd.c
> > > > index c7fd1a9d..979c1494 100644
> > > > --- a/fwd.c
> > > > +++ b/fwd.c
> > > > @@ -367,17 +367,59 @@ int fwd_rule_add(struct fwd_table *fwd, const struct fwd_rule *new)
> > > >   		     new->first, new->last);
> > > >   		return -EINVAL;
> > > >   	}
> > > > +	if (!new->first) {
> > > > +		warn("Forwarding rule attempts to map from port 0");
> > > > +		return -EINVAL;
> > > > +	}
> > > > +	if (!new->to ||
> > > > +	    (in_port_t)(new->to + new->last - new->first) < new->to) {
> > > > +		warn("Forwarding rule attempts to map to port 0");  
> > > 
> > > Not strictly true. We are also catching a range overflow case.
> > > Maybe "Forwarding rule maps to invalid port number"  
> > 
> > Well.. the specific overflow case is that the target range "wraps
> > around", thereby covering port 0, is the reasoning here.
> 
> ...and any other range overflow case is covered by the earlier check:
> 
> 	if (new->first > new->last) {
> 		warn("Rule has invalid port range %u-%u",
> 		     new->first, new->last);
> 		return -EINVAL;
> 	}
> 
> so I'm leaving this as it was, in v6.

Right, that's pretty much what I was suggesting.

-- 
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 --]

  reply	other threads:[~2026-05-04  4:25 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21  6:24 [PATCH v5 00/18] RFC: Dynamic configuration update implementation David Gibson
2026-04-21  6:24 ` [PATCH v5 01/18] conf, fwd: Stricter rule checking in fwd_rule_add() David Gibson
2026-04-25 13:31   ` Jon Maloy
2026-04-27  3:20     ` David Gibson
2026-05-03 21:56       ` Stefano Brivio
2026-05-04  4:24         ` David Gibson [this message]
2026-04-21  6:25 ` [PATCH v5 02/18] fwd_rule: Move ephemeral port probing to fwd_rule.c David Gibson
2026-04-21  6:25 ` [PATCH v5 03/18] fwd, conf: Move rule parsing code to fwd_rule.[ch] David Gibson
2026-04-24 21:59   ` Jon Maloy
2026-04-24 22:36   ` Jon Maloy
2026-05-03 21:56     ` Stefano Brivio
2026-04-21  6:25 ` [PATCH v5 04/18] fwd_rule: Move conflict checking back within fwd_rule_add() David Gibson
2026-04-21  6:25 ` [PATCH v5 05/18] fwd: Generalise fwd_rules_info() David Gibson
2026-04-21  6:25 ` [PATCH v5 06/18] pif: Limit pif names to 128 bytes David Gibson
2026-04-21  6:25 ` [PATCH v5 07/18] fwd_rule: Fix some format specifiers David Gibson
2026-04-21  6:25 ` [PATCH v5 08/18] tap, repair: Use SOCK_NONBLOCK and SOCK_CLOEXEC on Unix sockets David Gibson
2026-04-21  6:25 ` [PATCH v5 09/18] pesto: Introduce stub configuration tool David Gibson
2026-04-21  6:25 ` [PATCH v5 10/18] pesto, log: Share log.h (but not log.c) with pesto tool David Gibson
2026-04-21  6:25 ` [PATCH v5 11/18] pesto, conf: Have pesto connect to passt and check versions David Gibson
2026-04-26 13:45   ` Jon Maloy
2026-04-29  5:18     ` David Gibson
2026-05-03 21:56       ` Stefano Brivio
2026-04-21  6:25 ` [PATCH v5 12/18] pesto: Expose list of pifs to pesto and optionally display David Gibson
2026-04-26 13:45   ` Jon Maloy
2026-04-29  5:17     ` David Gibson
2026-05-03 21:56       ` Stefano Brivio
2026-04-21  6:25 ` [PATCH v5 13/18] ip: Prepare ip.[ch] for sharing with pesto tool David Gibson
2026-04-21  6:25 ` [PATCH v5 14/18] inany: Prepare inany.[ch] " David Gibson
2026-04-21  6:25 ` [PATCH v5 15/18] pesto: Read current ruleset from passt/pasta and optionally display it David Gibson
2026-04-24 22:37   ` Jon Maloy
2026-04-25  7:36     ` Stefano Brivio
2026-04-29  5:19       ` David Gibson
2026-05-03 21:56         ` Stefano Brivio
2026-04-21  6:25 ` [PATCH v5 16/18] pesto: Parse and add new rules from command line David Gibson
2026-04-21  6:25 ` [PATCH v5 17/18] pesto, conf: Send updated rules from pesto back to passt/pasta David Gibson
2026-04-24 22:38   ` Jon Maloy
2026-04-25  7:36     ` Stefano Brivio
2026-04-29  5:21       ` David Gibson
2026-05-03 21:56         ` Stefano Brivio
2026-04-21  6:25 ` [PATCH v5 18/18] conf, fwd: Allow switching to new rules received from pesto 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=afgfZXGUWwAQ1WDm@zatzit \
    --to=david@gibson.dropbear.id.au \
    --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).