From: patchwork-bot+netdevbpf@kernel.org
To: Evgenii Burenchev <evg28bur@yandex.ru>
Cc: stable@vger.kernel.org, gregkh@linuxfoundation.org,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, kees@kernel.org,
horms@kernel.org, bhelgaas@google.com, darinzon@amazon.com,
Yuval.Mintz@qlogic.com, manish.chopra@qlogic.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org
Subject: Re: [PATCH net v2] qed: fix division by zero in qed_init_wfq_param when all vports are configured
Date: Tue, 12 May 2026 01:48:42 +0000 [thread overview]
Message-ID: <177855052229.2567715.13167262625389092988.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260507145520.23106-1-evg28bur@yandex.ru>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 7 May 2026 17:55:17 +0300 you wrote:
> In qed_init_wfq_param(), variable non_requested_count can become zero
> when the number of vports with the configured flag set (including the
> current vport being configured) equals total num_vports. This happens
> when configuring the last unconfigured vport or when re-configuring
> an already configured vport.
>
> The function then calculates left_rate_per_vp = total_left_rate /
> non_requested_count, which causes division by zero.
>
> [...]
Here is the summary with links:
- [net,v2] qed: fix division by zero in qed_init_wfq_param when all vports are configured
https://git.kernel.org/netdev/net/c/be48e5fe51a5
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:[~2026-05-12 1:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 14:55 [PATCH net v2] qed: fix division by zero in qed_init_wfq_param when all vports are configured Evgenii Burenchev
2026-05-12 1:48 ` 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=177855052229.2567715.13167262625389092988.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Yuval.Mintz@qlogic.com \
--cc=andrew+netdev@lunn.ch \
--cc=bhelgaas@google.com \
--cc=darinzon@amazon.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=evg28bur@yandex.ru \
--cc=gregkh@linuxfoundation.org \
--cc=horms@kernel.org \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=manish.chopra@qlogic.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
/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