From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
andrew+netdev@lunn.ch, davem@davemloft.net,
donald.hunter@gmail.com, jiri@resnulli.us, shuah@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, mbloch@nvidia.com,
jiri@nvidia.com, cratiu@nvidia.com, gal@nvidia.com,
cjubran@nvidia.com
Subject: Re: [PATCH net-next] devlink: Fix excessive stack usage in rate TC bandwidth parsing
Date: Thu, 24 Jul 2025 02:00:42 +0000 [thread overview]
Message-ID: <175332244276.1844642.15811635856834310168.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1753175609-330621-1-git-send-email-tariqt@nvidia.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 22 Jul 2025 12:13:29 +0300 you wrote:
> From: Carolina Jubran <cjubran@nvidia.com>
>
> The devlink_nl_rate_tc_bw_parse function uses a large stack array for
> devlink attributes, which triggers a warning about excessive stack
> usage:
>
> net/devlink/rate.c: In function 'devlink_nl_rate_tc_bw_parse':
> net/devlink/rate.c:382:1: error: the frame size of 1648 bytes is larger than 1536 bytes [-Werror=frame-larger-than=]
>
> [...]
Here is the summary with links:
- [net-next] devlink: Fix excessive stack usage in rate TC bandwidth parsing
https://git.kernel.org/netdev/net-next/c/1bbdb81a9836
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-07-24 2:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 9:13 [PATCH net-next] devlink: Fix excessive stack usage in rate TC bandwidth parsing Tariq Toukan
2025-07-22 9:22 ` Jiri Pirko
2025-07-23 2:08 ` Jakub Kicinski
2025-07-24 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=175332244276.1844642.15811635856834310168.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=cjubran@nvidia.com \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=jiri@nvidia.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).