From: Stefano Brivio <sbrivio@redhat.com>
To: passt-dev@passt.top
Cc: Jon Maloy <jmaloy@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>,
Laurent Vivier <lvivier@redhat.com>,
Paul Holzinger <pholzing@redhat.com>
Subject: [PATCH v11 18/23] fwd_rule: Fix static checkers warnings in fwd_rule_add()
Date: Wed, 6 May 2026 23:31:50 +0200 [thread overview]
Message-ID: <20260506213155.1886983-19-sbrivio@redhat.com> (raw)
In-Reply-To: <20260506213155.1886983-1-sbrivio@redhat.com>
The new checks are actually sufficient but not enough for Coverity
Scan. Now that fwd->sock_count and new->last are affected or supplied
by clients, we need explicit (albeit redundant) checks on them.
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Reviewed-by: Laurent Vivier <lvivier@redhat.com>
---
fwd_rule.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/fwd_rule.c b/fwd_rule.c
index b55e4df..200f4b5 100644
--- a/fwd_rule.c
+++ b/fwd_rule.c
@@ -271,13 +271,24 @@ int fwd_rule_add(struct fwd_table *fwd, const struct fwd_rule *new)
warn("Too many rules (maximum %d)", ARRAY_SIZE(fwd->rules));
return -ENOSPC;
}
+
if ((fwd->sock_count + num) > ARRAY_SIZE(fwd->socks)) {
warn("Rules require too many listening sockets (maximum %d)",
ARRAY_SIZE(fwd->socks));
return -ENOSPC;
}
+ /* Redundant (see check just above), to make static checkers happy */
+ if (fwd->sock_count > ARRAY_SIZE(fwd->socks))
+ return -ENOSPC;
fwd->rulesocks[fwd->count] = &fwd->socks[fwd->sock_count];
+
+ /* Redundant, but not for static checkers, that might be missing that
+ * due to the check on 'num' above against ARRAY_SIZE(fwd->socks), we
+ * have a proper upper bound for new->last in the loop below.
+ */
+ if (new->last > ARRAY_SIZE(fwd->socks) + new->first)
+ return -ENOSPC;
for (port = new->first; port <= new->last; port++)
fwd->rulesocks[fwd->count][port - new->first] = -1;
--
2.43.0
next prev parent reply other threads:[~2026-05-06 21:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 21:31 [PATCH v11 00/23] Dynamic configuration update implementation Stefano Brivio
2026-05-06 21:31 ` [PATCH v11 01/23] conf, fwd: Stricter rule checking in fwd_rule_add() Stefano Brivio
2026-05-06 21:31 ` [PATCH v11 02/23] fwd_rule: Move ephemeral port probing to fwd_rule.c Stefano Brivio
2026-05-06 21:31 ` [PATCH v11 03/23] fwd, conf: Move rule parsing code to fwd_rule.[ch] Stefano Brivio
2026-05-06 21:31 ` [PATCH v11 04/23] fwd_rule: Move conflict checking back within fwd_rule_add() Stefano Brivio
2026-05-06 21:31 ` [PATCH v11 05/23] fwd: Generalise fwd_rules_info() Stefano Brivio
2026-05-06 21:31 ` [PATCH v11 06/23] pif: Limit pif names to 128 bytes Stefano Brivio
2026-05-06 21:31 ` [PATCH v11 07/23] fwd_rule: Fix some format specifiers Stefano Brivio
2026-05-06 21:31 ` [PATCH v11 08/23] pesto: Introduce stub configuration tool Stefano Brivio
2026-05-06 21:31 ` [PATCH v11 09/23] pesto, log: Share log.h (but not log.c) with pesto tool Stefano Brivio
2026-05-06 23:41 ` David Gibson
2026-05-06 21:31 ` [PATCH v11 10/23] pesto, conf: Have pesto connect to passt and check versions Stefano Brivio
2026-05-06 21:31 ` [PATCH v11 11/23] pesto: Expose list of pifs to pesto and display them Stefano Brivio
2026-05-06 21:31 ` [PATCH v11 12/23] ip: Prepare ip.[ch] for sharing with pesto tool Stefano Brivio
2026-05-06 21:31 ` [PATCH v11 13/23] inany: Prepare inany.[ch] " Stefano Brivio
2026-05-06 21:31 ` [PATCH v11 14/23] pesto: Read current ruleset from passt/pasta and optionally display it Stefano Brivio
2026-05-06 21:31 ` [PATCH v11 15/23] pesto: Parse and add new rules from command line Stefano Brivio
2026-05-06 21:31 ` [PATCH v11 16/23] pesto, conf: Send updated rules from pesto back to passt/pasta Stefano Brivio
2026-05-06 21:31 ` [PATCH v11 17/23] conf, fwd: Allow switching to new rules received from pesto Stefano Brivio
2026-05-06 21:31 ` Stefano Brivio [this message]
2026-05-06 21:31 ` [PATCH v11 19/23] pesto, conf, fwd_rule: Add options and modes to add, delete, clear rules Stefano Brivio
2026-05-06 23:51 ` David Gibson
2026-05-07 2:10 ` Stefano Brivio
2026-05-07 3:18 ` David Gibson
2026-05-06 21:31 ` [PATCH v11 20/23] apparmor: Add policy file for pesto Stefano Brivio
2026-05-06 21:31 ` [PATCH v11 21/23] selinux: Add file context and type enforcement " Stefano Brivio
2026-05-06 21:31 ` [PATCH v11 22/23] fedora: Install pesto, its SELinux policy, and the man page from the spec file Stefano Brivio
2026-05-06 21:31 ` [PATCH v11 23/23] hooks: Copy static build of pesto and related man page to server 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=20260506213155.1886983-19-sbrivio@redhat.com \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=jmaloy@redhat.com \
--cc=lvivier@redhat.com \
--cc=passt-dev@passt.top \
--cc=pholzing@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).