From: patchwork-bot+netdevbpf@kernel.org
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
keescook+coverity-bot@chromium.org
Subject: Re: [PATCH] net: ethernet: renesas: rswitch: Fix endless loop in error paths
Date: Wed, 09 Nov 2022 02:00:15 +0000 [thread overview]
Message-ID: <166795921555.12027.4687508688577621860.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221107081021.2955122-1-yoshihiro.shimoda.uh@renesas.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 7 Nov 2022 17:10:21 +0900 you wrote:
> Coverity reported that the error path in rswitch_gwca_queue_alloc_skb()
> has an issue to cause endless loop. So, fix the issue by changing
> variables' types from u32 to int. After changed the types,
> rswitch_tx_free() should use rswitch_get_num_cur_queues() to
> calculate number of current queues.
>
> Reported-by: coverity-bot <keescook+coverity-bot@chromium.org>
> Addresses-Coverity-ID: 1527147 ("Control flow issues")
> Fixes: 3590918b5d07 ("net: ethernet: renesas: Add support for "Ethernet Switch"")
> Signed-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
>
> [...]
Here is the summary with links:
- net: ethernet: renesas: rswitch: Fix endless loop in error paths
https://git.kernel.org/netdev/net-next/c/380f9acdf747
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-11-09 2:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 8:10 [PATCH] net: ethernet: renesas: rswitch: Fix endless loop in error paths Yoshihiro Shimoda
2022-11-09 2:00 ` patchwork-bot+netdevbpf [this message]
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=166795921555.12027.4687508688577621860.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=keescook+coverity-bot@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yoshihiro.shimoda.uh@renesas.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