From: Saeed Mahameed <saeed@kernel.org>
To: "Jean-François Roy" <jf@devklog.net>
Cc: netdev@vger.kernel.org
Subject: Re: mlx5e_xmit: detected field-spanning write (6.12.16)
Date: Tue, 25 Feb 2025 11:48:33 -0800 [thread overview]
Message-ID: <Z74ekZy_WnOhAQrD@x130> (raw)
In-Reply-To: <CAE8T=_Go-A_W9j18oO+5S52pXKwgFDcR8XgHiywwSRSZmO2LEw@mail.gmail.com>
On 25 Feb 08:37, Jean-François Roy wrote:
>I'm regularly seeing field-spanning write dumps from the mlx5 driver
>on one of my Talos Linux + Cilium nodes running Linux 6.12.16. I don't
>know if this is caused by a bug in one of Cilum's bpf programs or if
>it's a legitimate issue with the driver.
>
>kantai1: kern: warning: [2025-02-25T16:19:43.741311529Z]:
>------------[ cut here ]------------
>kantai1: kern: warning: [2025-02-25T16:19:43.741322529Z]: memcpy:
>detected field-spanning write (size 32) of single field "h6 + 1" at
>drivers/net/ethernet/mellanox/mlx5/core/en_tx.c:469 (size 0)
>kantai1: kern: warning: [2025-02-25T16:19:43.741350529Z]: WARNING:
>CPU: 2 PID: 5273 at
>drivers/net/ethernet/mellanox/mlx5/core/en_tx.c:469
>mlx5e_xmit+0x99b/0xe00 [mlx5_core]
False alarm
Can you please test this diff:
git diff
diff --git a/drivers/net/ethernet/mellanox/mlx5/core/en_tx.c
b/drivers/net/ethernet/mellanox/mlx5/core/en_tx.c
index f8c7912abe0e..40ed9d37edf4 100644
--- a/drivers/net/ethernet/mellanox/mlx5/core/en_tx.c
+++ b/drivers/net/ethernet/mellanox/mlx5/core/en_tx.c
@@ -448,7 +448,7 @@ mlx5e_sq_xmit_wqe(struct mlx5e_txqsq *sq, struct
sk_buff *skb,
eseg->mss = attr->mss;
if (ihs) {
- u8 *start = eseg->inline_hdr.start;
+ u8 *start = eseg->inline_hdr.data;
if (unlikely(attr->hopbyhop)) {
/* remove the HBH header.
Thanks,
Saeed.
prev parent reply other threads:[~2025-02-25 19:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 16:37 mlx5e_xmit: detected field-spanning write (6.12.16) Jean-François Roy
2025-02-25 19:48 ` Saeed Mahameed [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=Z74ekZy_WnOhAQrD@x130 \
--to=saeed@kernel.org \
--cc=jf@devklog.net \
--cc=netdev@vger.kernel.org \
/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