From: ALOK TIWARI <alok.a.tiwari@oracle.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: sgoutham@marvell.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
darren.kenny@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH net-next v2] net: thunderx: Fix format-truncation warning in bgx_acpi_match_id()
Date: Fri, 11 Jul 2025 15:47:43 +0530 [thread overview]
Message-ID: <7334d51a-65d3-43ed-8a33-eedeeb810045@oracle.com> (raw)
In-Reply-To: <20250710153422.6adae255@kernel.org>
On 7/11/2025 4:04 AM, Jakub Kicinski wrote:
> On Tue, 8 Jul 2025 10:52:43 -0700 Alok Tiwari wrote:
>> Increase the buffer size from 5 to 8 and use sizeof(bgx_sel) in
>> snprintf() to ensure safety and suppress the warning.
>>
>> Build warning:
>> CC drivers/net/ethernet/cavium/thunder/thunder_bgx.o
>> drivers/net/ethernet/cavium/thunder/thunder_bgx.c: In function
>> ‘bgx_acpi_match_id’:
>> drivers/net/ethernet/cavium/thunder/thunder_bgx.c:1434:27: error: ‘%d’
>> directive output may be truncated writing between 1 and 3 bytes into a
>> region of size 2 [-Werror=format-truncation=]
>> snprintf(bgx_sel, 5, "BGX%d", bgx->bgx_id);
>> ^~
>> drivers/net/ethernet/cavium/thunder/thunder_bgx.c:1434:23: note:
>> directive argument in the range [0, 255]
>> snprintf(bgx_sel, 5, "BGX%d", bgx->bgx_id);
>> ^~~~~~~
>> drivers/net/ethernet/cavium/thunder/thunder_bgx.c:1434:2: note:
>> ‘snprintf’ output between 5 and 7 bytes into a destination of size 5
>> snprintf(bgx_sel, 5, "BGX%d", bgx->bgx_id);
>
> Hm, why are you making it 8 when the max length is 7 ? 🤔️
yes, 7 is max range. I will send v3 with this change.
Thanks,
Alok
prev parent reply other threads:[~2025-07-11 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 17:52 [PATCH net-next v2] net: thunderx: Fix format-truncation warning in bgx_acpi_match_id() Alok Tiwari
2025-07-09 10:08 ` Simon Horman
2025-07-10 22:34 ` Jakub Kicinski
2025-07-11 10:17 ` ALOK TIWARI [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=7334d51a-65d3-43ed-8a33-eedeeb810045@oracle.com \
--to=alok.a.tiwari@oracle.com \
--cc=andrew+netdev@lunn.ch \
--cc=darren.kenny@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sgoutham@marvell.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).