public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
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 v8 18/19] fwd_rule: Fix static checkers warnings in fwd_rule_add()
Date: Wed, 6 May 2026 09:18:55 +0200	[thread overview]
Message-ID: <43a44aa7-c974-403f-96aa-d860b4c614e0@redhat.com> (raw)
In-Reply-To: <20260505234719.1437340-19-sbrivio@redhat.com>

On 5/6/26 01:47, Stefano Brivio wrote:
> 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 | 9 +++++++++
>   1 file changed, 9 insertions(+)
> 
> diff --git a/fwd_rule.c b/fwd_rule.c
> index b55e4df..03e8e80 100644
> --- a/fwd_rule.c
> +++ b/fwd_rule.c
> @@ -271,13 +271,22 @@ 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, 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 ('num' checked above), but not for static checkers */
> +	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;
>   


  reply	other threads:[~2026-05-06  7:19 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05 23:47 [PATCH v8 00/19] Dynamic configuration update implementation Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 01/19] conf, fwd: Stricter rule checking in fwd_rule_add() Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 02/19] fwd_rule: Move ephemeral port probing to fwd_rule.c Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 03/19] fwd, conf: Move rule parsing code to fwd_rule.[ch] Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 04/19] fwd_rule: Move conflict checking back within fwd_rule_add() Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 05/19] fwd: Generalise fwd_rules_info() Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 06/19] pif: Limit pif names to 128 bytes Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 07/19] fwd_rule: Fix some format specifiers Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 08/19] pesto: Introduce stub configuration tool Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 09/19] pesto, log: Share log.h (but not log.c) with pesto tool Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 10/19] pesto, conf: Have pesto connect to passt and check versions Stefano Brivio
2026-05-06  5:38   ` David Gibson
2026-05-06  7:06     ` Laurent Vivier
2026-05-06  7:41       ` David Gibson
2026-05-06  7:55     ` Stefano Brivio
2026-05-06  8:21       ` David Gibson
2026-05-06  8:30         ` Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 11/19] pesto: Expose list of pifs to pesto and display them Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 12/19] ip: Prepare ip.[ch] for sharing with pesto tool Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 13/19] inany: Prepare inany.[ch] " Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 14/19] pesto: Read current ruleset from passt/pasta and optionally display it Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 15/19] pesto: Parse and add new rules from command line Stefano Brivio
2026-05-06  7:13   ` Laurent Vivier
2026-05-06  9:15     ` Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 16/19] pesto, conf: Send updated rules from pesto back to passt/pasta Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 17/19] conf, fwd: Allow switching to new rules received from pesto Stefano Brivio
2026-05-06  7:15   ` Laurent Vivier
2026-05-06  8:12   ` Laurent Vivier
2026-05-06  8:23     ` David Gibson
2026-05-06  8:39     ` Stefano Brivio
2026-05-06  8:49       ` Stefano Brivio
2026-05-06  8:52         ` David Gibson
2026-05-06  9:11           ` Laurent Vivier
2026-05-06 12:11             ` Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 18/19] fwd_rule: Fix static checkers warnings in fwd_rule_add() Stefano Brivio
2026-05-06  7:18   ` Laurent Vivier [this message]
2026-05-05 23:47 ` [PATCH v8 19/19] pesto, conf, fwd_rule: Add options and modes to add, delete, clear rules Stefano Brivio
2026-05-06  6:45   ` David Gibson
2026-05-06  8:22     ` Stefano Brivio
2026-05-06  8:48       ` David Gibson
2026-05-06  8:56         ` Stefano Brivio
2026-05-06  9:22           ` David Gibson
2026-05-06 12:52           ` Stefano Brivio
2026-05-06  6:53 ` [PATCH v8 00/19] 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=43a44aa7-c974-403f-96aa-d860b4c614e0@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).