From: patchwork-bot+netdevbpf@kernel.org
To: Danielle Costantino <dcostantino@meta.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, gal@nvidia.com,
tariqt@nvidia.com, pabeni@redhat.com, saeedm@nvidia.com,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] net/mlx5e: Fix validation logic in rate limiting
Date: Wed, 26 Nov 2025 00:50:06 +0000 [thread overview]
Message-ID: <176411820601.971301.9105241183448628229.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251124180043.2314428-1-dcostantino@meta.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 24 Nov 2025 10:00:43 -0800 you wrote:
> The rate limiting validation condition currently checks the output
> variable max_bw_value[i] instead of the input value
> maxrate->tc_maxrate[i]. This causes the validation to compare an
> uninitialized or stale value rather than the actual requested rate.
>
> The condition should check the input rate to properly validate against
> the upper limit:
>
> [...]
Here is the summary with links:
- [net] net/mlx5e: Fix validation logic in rate limiting
https://git.kernel.org/netdev/net/c/d2099d9f16db
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:[~2025-11-26 0:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 18:00 [PATCH net] net/mlx5e: Fix validation logic in rate limiting Danielle Costantino
2025-11-24 18:37 ` Gal Pressman
2025-11-26 0:50 ` 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=176411820601.971301.9105241183448628229.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dcostantino@meta.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.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