From: Konrad Leszczynski <konrad.leszczynski@intel.com>
To: Andrew Lunn <andrew@lunn.ch>,
Sebastian Basierski <sebastian.basierski@intel.com>
Cc: Jakub Kicinski <kuba@kernel.org>, <davem@davemloft.net>,
<andrew+netdev@lunn.ch>, <edumazet@google.com>,
<pabeni@redhat.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <cezary.rojewski@intel.com>
Subject: Re: [PATCH net 1/3] net: stmmac: replace memcpy with strscpy in ethtool
Date: Mon, 15 Sep 2025 15:18:35 +0200 [thread overview]
Message-ID: <b8a3e3e7-295a-4cde-9d2f-73b5df4200d9@intel.com> (raw)
In-Reply-To: <f6cac0bd-3a07-40c3-b07b-f1c7f3b27f45@lunn.ch>
On 04-Sep-25 21:18, Andrew Lunn wrote:
> On Thu, Sep 04, 2025 at 08:53:03PM +0200, Sebastian Basierski wrote:
>> On 9/1/2025 9:59 PM, Jakub Kicinski wrote:
>>> On Thu, 28 Aug 2025 12:02:35 +0200 Konrad Leszczynski wrote:
>>>> Fix kernel exception by replacing memcpy with strscpy when used with
>>>> safety feature strings in ethtool logic.
>>>>
>>>> [ +0.000023] BUG: KASAN: global-out-of-bounds in stmmac_get_strings+0x17d/0x520 [stmmac]
>>>> [ +0.000115] Read of size 32 at addr ffffffffc0cfab20 by task ethtool/2571
>>> If you hit this with upstream code please mention which string
>>> is not padded. If this can't happen with upstream platforms --
>>> there is no upstream bug. BTW ethtool_puts() is a better choice.
>> Hi Jakub,
>> Sorry for late answer to your review.
>> I double checked and made sure this bug reproduces on upstream platform.
>> Bug seems to appear on first string - i will add this information to commit
>> message.
> By first string, do you mean "Application Transmit Interface Parity
> Check Error"?
>
> I think it also would be better to change dwmac5_error_desc, so that
> it uses char stat_string[ETH_GSTRING_LEN] __nonstring; like
> stmmac_stats.
>
> Andrew
Hi Andrew,
Thanks for your comments. We can add the change as a new patch as part
of this patchset. Would that be ok?
next prev parent reply other threads:[~2025-09-15 13:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 10:02 [PATCH net 0/3] net: stmmac: misc fixes Konrad Leszczynski
2025-08-28 10:02 ` [PATCH net 1/3] net: stmmac: replace memcpy with strscpy in ethtool Konrad Leszczynski
2025-08-28 13:29 ` Vadim Fedorenko
2025-09-01 19:59 ` Jakub Kicinski
2025-09-04 18:53 ` Sebastian Basierski
2025-09-04 19:18 ` Andrew Lunn
2025-09-15 13:18 ` Konrad Leszczynski [this message]
2025-08-28 10:02 ` [PATCH net 2/3] net: stmmac: correct Tx descriptors debugfs prints Konrad Leszczynski
2025-08-28 13:34 ` Vadim Fedorenko
2025-09-01 20:01 ` Jakub Kicinski
2025-09-04 18:54 ` Sebastian Basierski
2025-09-15 12:54 ` Konrad Leszczynski
2025-09-15 15:05 ` Jakub Kicinski
2025-08-28 10:02 ` [PATCH net 3/3] net: stmmac: check if interface is running before TC block setup Konrad Leszczynski
2025-08-28 13:39 ` Vadim Fedorenko
2025-09-01 20:03 ` Jakub Kicinski
2025-09-04 19:01 ` Sebastian Basierski
2025-09-05 1:56 ` Jakub Kicinski
2025-09-09 18:47 ` Sebastian Basierski
2025-09-16 23:29 ` Jakub Kicinski
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=b8a3e3e7-295a-4cde-9d2f-73b5df4200d9@intel.com \
--to=konrad.leszczynski@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=cezary.rojewski@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sebastian.basierski@intel.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).