From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: "Oleksandr Makarov [GL]" <Oleksandr.Makarov@qsc.com>
Cc: Eric Dumazet <edumazet@google.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-stm32@st-md-mailman.stormreply.com"
<linux-stm32@st-md-mailman.stormreply.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: BUG: UDP Packet Corruption Issue with stmmac Driver on Linux 5.15.21-rt30
Date: Sun, 19 Jan 2025 15:13:33 +0000 [thread overview]
Message-ID: <Z40WnTc09OOnCZ3p@shell.armlinux.org.uk> (raw)
In-Reply-To: <BLAPR16MB3924E3DF8703DDCBC1C033BBF0E42@BLAPR16MB3924.namprd16.prod.outlook.com>
On Sun, Jan 19, 2025 at 12:46:54PM +0000, Oleksandr Makarov [GL] wrote:
> I bisected kernel from 6.12, where the issue with trimming fragmented UDP packets was fixed, down to 5.15.21.
>
> I have identified that commit "47f753c1108e287edb3e27fad8a7511a9d55578e net: stmmac: disable Split Header (SPH) for Intel platforms" is fixing the problem.
It sounds like you're saying that it's been fixed on mainline, but the
fix hasn't been backported to 5.15.21. Well, it won't ever be. 5.15.21
is one instance of the 5.15-stable kernel tree, and the 5.15-stable
tree is now at 5.15.176.
Try moving your stable kernel forward. If you're locked in to 5.15.21
by an upstream vendor, then you need to complain to them.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
prev parent reply other threads:[~2025-01-19 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 11:40 BUG: UDP Packet Corruption Issue with stmmac Driver on Linux 5.15.21-rt30 Oleksandr Makarov [GL]
2024-08-05 14:02 ` Eric Dumazet
2024-08-05 14:16 ` Oleksandr Makarov [GL]
2024-09-18 13:06 ` Oleksandr Makarov [GL]
2025-01-19 12:46 ` Oleksandr Makarov [GL]
2025-01-19 15:13 ` Russell King (Oracle) [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=Z40WnTc09OOnCZ3p@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=Oleksandr.Makarov@qsc.com \
--cc=alexandre.torgue@foss.st.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--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).