From: Laurent Vivier <lvivier@redhat.com>
To: Stefano Brivio <sbrivio@redhat.com>, passt-dev@passt.top
Cc: Jon Maloy <jmaloy@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH v6 01/18] conf, fwd: Stricter rule checking in fwd_rule_add()
Date: Mon, 4 May 2026 10:38:51 +0200 [thread overview]
Message-ID: <c4fdb2fb-e38b-4d76-bfff-b46e0af8fbeb@redhat.com> (raw)
In-Reply-To: <20260503215601.823029-2-sbrivio@redhat.com>
On 5/3/26 23:55, Stefano Brivio wrote:
> From: David Gibson <david@gibson.dropbear.id.au>
>
> 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.
>
> That won't be enough when we can get rules inserted by a dynamic update
> client without going through the existing parsing code. So, add stricter
> checks to fwd_rule_add(), which is now possible thanks to the capabilities
> bits in the struct fwd_table. Where those duplicate existing checks in the
> callers, remove the old copies.
>
> 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>
> ---
> conf.c | 21 ---------------------
> fwd.c | 52 +++++++++++++++++++++++++++++++++++++++++++++++-----
> 2 files changed, 47 insertions(+), 26 deletions(-)
>
> diff --git a/conf.c b/conf.c
> index 6e884e5..b470b0d 100644
> --- a/conf.c
> +++ b/conf.c
> @@ -176,8 +176,6 @@ static void conf_ports_range_except(struct fwd_table *fwd, uint8_t proto,
> die("Invalid interface name: %s", ifname);
> }
>
> - assert(first != 0);
> -
> for (base = first; base <= last; base++) {
> if (exclude && bitmap_isset(exclude, base))
> continue;
> @@ -310,10 +308,6 @@ static void conf_ports_spec(struct fwd_table *fwd, uint8_t proto,
> if (p != ep) /* Garbage after the ranges */
> goto bad;
>
> - if (orig_range.first == 0) {
> - die("Can't forward port 0 included in '%s'", spec);
> - }
> -
> conf_ports_range_except(fwd, proto, addr, ifname,
> orig_range.first, orig_range.last,
> exclude,
> @@ -356,11 +350,6 @@ static void conf_ports(char optname, const char *optarg, struct fwd_table *fwd)
> return;
> }
>
> - if (proto == IPPROTO_TCP && !(fwd->caps & FWD_CAP_TCP))
> - die("TCP port forwarding requested but TCP is disabled");
> - if (proto == IPPROTO_UDP && !(fwd->caps & FWD_CAP_UDP))
> - die("UDP port forwarding requested but UDP is disabled");
> -
> strncpy(buf, optarg, sizeof(buf) - 1);
>
> if ((spec = strchr(buf, '/'))) {
> @@ -405,16 +394,6 @@ static void conf_ports(char optname, const char *optarg, struct fwd_table *fwd)
> addr = NULL;
> }
>
> - if (addr) {
> - if (!(fwd->caps & FWD_CAP_IPV4) && inany_v4(addr)) {
> - die("IPv4 is disabled, can't use -%c %s",
> - optname, optarg);
> - } else if (!(fwd->caps & FWD_CAP_IPV6) && !inany_v4(addr)) {
> - die("IPv6 is disabled, can't use -%c %s",
> - optname, optarg);
> - }
> - }
> -
> if (optname == 'T' || optname == 'U') {
> assert(!addr && !ifname);
>
> diff --git a/fwd.c b/fwd.c
> index c7fd1a9..979c149 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");
> + return -EINVAL;
> + }
> if (new->flags & ~allowed_flags) {
> warn("Rule has invalid flags 0x%hhx",
> new->flags & ~allowed_flags);
> return -EINVAL;
> }
> - if (new->flags & FWD_DUAL_STACK_ANY &&
> - !inany_equals(&new->addr, &inany_any6)) {
> - char astr[INANY_ADDRSTRLEN];
> + if (new->flags & FWD_DUAL_STACK_ANY) {
> + if (!inany_equals(&new->addr, &inany_any6)) {
> + char astr[INANY_ADDRSTRLEN];
>
> - warn("Dual stack rule has non-wildcard address %s",
> - inany_ntop(&new->addr, astr, sizeof(astr)));
> + warn("Dual stack rule has non-wildcard address %s",
> + inany_ntop(&new->addr, astr, sizeof(astr)));
> + return -EINVAL;
> + }
> + if (!(fwd->caps & FWD_CAP_IPV4)) {
> + warn("Dual stack forward, but IPv4 not enabled");
> + return -EINVAL;
> + }
> + if (!(fwd->caps & FWD_CAP_IPV6)) {
> + warn("Dual stack forward, but IPv6 not enabled");
> + return -EINVAL;
> + }
> + } else {
> + if (inany_v4(&new->addr) && !(fwd->caps & FWD_CAP_IPV4)) {
> + warn("IPv4 forward, but IPv4 not enabled");
> + return -EINVAL;
> + }
> + if (!inany_v4(&new->addr) && !(fwd->caps & FWD_CAP_IPV6)) {
> + warn("IPv6 forward, but IPv6 not enabled");
> + return -EINVAL;
> + }
> + }
> + if (new->proto == IPPROTO_TCP) {
> + if (!(fwd->caps & FWD_CAP_TCP)) {
> + warn("Can't add TCP forwarding rule, TCP not enabled");
> + return -EINVAL;
> + }
> + } else if (new->proto == IPPROTO_UDP) {
> + if (!(fwd->caps & FWD_CAP_UDP)) {
> + warn("Can't add UDP forwarding rule, UDP not enabled");
> + return -EINVAL;
> + }
> + } else {
> + warn("Unsupported protocol 0x%hhx (%s) for forwarding rule",
> + new->proto, ipproto_name(new->proto));
> return -EINVAL;
> }
>
next prev parent reply other threads:[~2026-05-04 8:38 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 [this message]
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
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=c4fdb2fb-e38b-4d76-bfff-b46e0af8fbeb@redhat.com \
--to=lvivier@redhat.com \
--cc=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).