From: patchwork-bot+netdevbpf@kernel.org
To: Simon Horman <horms@kernel.org>
Cc: irusskikh@marvell.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: atlantic: Avoid warning about potential string truncation
Date: Fri, 23 Aug 2024 00:00:33 +0000 [thread overview]
Message-ID: <172437123351.2508974.14515879032118431427.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240821-atlantic-str-v1-1-fa2cfe38ca00@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 21 Aug 2024 16:58:57 +0100 you wrote:
> W=1 builds with GCC 14.2.0 warn that:
>
> .../aq_ethtool.c:278:59: warning: ‘%d’ directive output may be truncated writing between 1 and 11 bytes into a region of size 6 [-Wformat-truncation=]
> 278 | snprintf(tc_string, 8, "TC%d ", tc);
> | ^~
> .../aq_ethtool.c:278:56: note: directive argument in the range [-2147483641, 254]
> 278 | snprintf(tc_string, 8, "TC%d ", tc);
> | ^~~~~~~
> .../aq_ethtool.c:278:33: note: ‘snprintf’ output between 5 and 15 bytes into a destination of size 8
> 278 | snprintf(tc_string, 8, "TC%d ", tc);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> [...]
Here is the summary with links:
- [net-next] net: atlantic: Avoid warning about potential string truncation
https://git.kernel.org/netdev/net-next/c/5874e0c9f256
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:[~2024-08-23 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 15:58 [PATCH net-next] net: atlantic: Avoid warning about potential string truncation Simon Horman
2024-08-23 0: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=172437123351.2508974.14515879032118431427.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=irusskikh@marvell.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).