From: Jakub Kicinski <kuba@kernel.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Stefan Chulski <stefanc@marvell.com>,
Marcin Wojtas <marcin.s.wojtas@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH net] net: mvpp2: Don't re-use loop iterator
Date: Thu, 25 Jul 2024 08:04:40 -0700 [thread overview]
Message-ID: <20240725080440.41c2fd97@kernel.org> (raw)
In-Reply-To: <eaa8f403-7779-4d81-973d-a9ecddc0bf6f@stanley.mountain>
On Wed, 24 Jul 2024 11:06:56 -0500 Dan Carpenter wrote:
> This function has a nested loop. The problem is that both the inside
> and outside loop use the same variable as an iterator. I found this
> via static analysis so I'm not sure the impact. It could be that it
> loops forever or, more likely, the loop exits early.
> diff --git a/drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c b/drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c
> index 8c45ad983abc..0d62a33afa80 100644
> --- a/drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c
> +++ b/drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c
> @@ -953,13 +953,13 @@ static void mvpp2_bm_pool_update_fc(struct mvpp2_port *port,
> static void mvpp2_bm_pool_update_priv_fc(struct mvpp2 *priv, bool en)
> {
> struct mvpp2_port *port;
> - int i;
> + int i, j;
>
> for (i = 0; i < priv->port_count; i++) {
> port = priv->port_list[i];
> if (port->priv->percpu_pools) {
> - for (i = 0; i < port->nrxqs; i++)
> - mvpp2_bm_pool_update_fc(port, &port->priv->bm_pools[i],
> + for (j = 0; j < port->nrxqs; j++)
> + mvpp2_bm_pool_update_fc(port, &port->priv->bm_pools[j],
> port->tx_fc & en);
> } else {
> mvpp2_bm_pool_update_fc(port, port->pool_long, port->tx_fc & en);
Stefan, can you comment? priv->bm_pools are global (not per port)
AFAICT, so this may be semi-intentional.
next prev parent reply other threads:[~2024-07-25 15:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 16:06 [PATCH net] net: mvpp2: Don't re-use loop iterator Dan Carpenter
2024-07-24 18:50 ` Simon Horman
2024-07-25 15:04 ` Jakub Kicinski [this message]
2024-07-30 16:20 ` patchwork-bot+netdevbpf
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=20240725080440.41c2fd97@kernel.org \
--to=kuba@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marcin.s.wojtas@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stefanc@marvell.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.
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 NNTP newsgroup(s).