From: Jon Maloy <jmaloy@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>,
Stefano Brivio <sbrivio@redhat.com>,
passt-dev@passt.top
Subject: Re: [PATCH v5 01/18] conf, fwd: Stricter rule checking in fwd_rule_add()
Date: Sat, 25 Apr 2026 15:31:52 [thread overview]
Message-ID: <a51ca0e5-f75e-4e98-95c5-10832c3fd1c4@redhat.com> (raw)
In-Reply-To: <20260421062516.2601204-2-david@gibson.dropbear.id.au>
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"
/jon
> + 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-04-25 15:31 UTC|newest]
Thread overview: 33+ 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 [this message]
2026-04-27 3:20 ` David Gibson
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-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-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-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-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-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=a51ca0e5-f75e-4e98-95c5-10832c3fd1c4@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).