From: Jacob Keller <jacob.e.keller@intel.com>
To: David Laight <david.laight.linux@gmail.com>,
Rosen Penev <rosenp@gmail.com>
Cc: <netdev@vger.kernel.org>,
Michael Chan <michael.chan@broadcom.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net: b44: use ethtool_puts
Date: Thu, 4 Jun 2026 12:09:24 -0700 [thread overview]
Message-ID: <c4e85589-28ab-432b-8148-74ceeb9facaf@intel.com> (raw)
In-Reply-To: <20260604095010.35476abb@pumpkin>
On 6/4/2026 1:50 AM, David Laight wrote:
> On Sat, 30 May 2026 17:03:34 -0700
> Rosen Penev <rosenp@gmail.com> wrote:
>
>> There's a subtle error with the memcpy here, where b44_gstrings should
>> not be dereferenced. Dereferening causes the following error with W=1:
>
> The definition is:
> static const char b44_gstrings[][ETH_GSTRING_LEN] = ...
>
> There is nothing wrong with using memcpy().
>
>>
>> In file included from drivers/net/ethernet/broadcom/b44.c:17:
>> In file included from ./include/linux/module.h:18:
>> In file included from ./include/linux/kmod.h:9:
>> In file included from ./include/linux/umh.h:4:
>> In file included from ./include/linux/gfp.h:7:
>> In file included from ./include/linux/mmzone.h:8:
>> In file included from ./include/linux/spinlock.h:56:
>> In file included from ./include/linux/preempt.h:79:
>> In file included from ./arch/powerpc/include/asm/preempt.h:5:
>> In file included from ./include/asm-generic/preempt.h:5:
>> In file included from ./include/linux/thread_info.h:23:
>> In file included from ./arch/powerpc/include/asm/current.h:13:
>> In file included from ./arch/powerpc/include/asm/paca.h:16:
>> In file included from ./include/linux/string.h:386:
>> ./include/linux/fortify-string.h:578:4: error: call to
>> '__read_overflow2_field' declared with 'warning' attribute: detected read
>> beyond size of field (2nd parameter); maybe use>
>> 578 | __read_overflow2_field(q_size_field, size);
>> | ^
>>
>> Instead of fixing the memcpy, use ethtool_puts, which is the proper
>> helper for printing ethtool gstrings.
>
> ethtool_puts() lets you pass short strings as well as ones that don't
> contain a '\0' terminator.
> It isn't needed here because all the strings are already padded.
>
While not strictly needed, I think use of ethtool_puts in the ethtool
strings code makes sense and is easier to understand that it is correct.
memcpy is likely faster, but I don't think that speed is critical here.
>>
>> Signed-off-by: Rosen Penev <rosenp@gmail.com>
>> ---
>> drivers/net/ethernet/broadcom/b44.c | 10 +++++-----
>> 1 file changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/net/ethernet/broadcom/b44.c b/drivers/net/ethernet/broadcom/b44.c
>> index 90df02e0039c..f994636fbd5f 100644
>> --- a/drivers/net/ethernet/broadcom/b44.c
>> +++ b/drivers/net/ethernet/broadcom/b44.c
>> @@ -2031,11 +2031,11 @@ static int b44_set_pauseparam(struct net_device *dev,
>>
>> static void b44_get_strings(struct net_device *dev, u32 stringset, u8 *data)
>> {
>> - switch(stringset) {
>> - case ETH_SS_STATS:
>> - memcpy(data, *b44_gstrings, sizeof(b44_gstrings));
>
> Just remove the * or replace with an & - either is valid.
> The existing code is reading b44_gstrings[0] so overruns into the following
> strings.
>
Right, that would have been the simplest fix.
prev parent reply other threads:[~2026-06-04 19:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-31 0:03 [PATCH] net: b44: use ethtool_puts Rosen Penev
2026-06-04 1:14 ` patchwork-bot+netdevbpf
2026-06-04 8:50 ` David Laight
2026-06-04 19:09 ` Jacob Keller [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=c4e85589-28ab-432b-8148-74ceeb9facaf@intel.com \
--to=jacob.e.keller@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=david.laight.linux@gmail.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rosenp@gmail.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