From: Alex Elder <elder@riscstar.com>
To: maxime.chevallier@bootlin.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Cc: sashiko-bot@kernel.org, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com,
linux-stm32@st-md-mailman.stormreply.com, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH net-next v2 0/2] net: stmmac: DMA address handling fixes
Date: Wed, 12 Aug 2026 11:38:29 -0500 [thread overview]
Message-ID: <20260812163832.271742-1-elder@riscstar.com> (raw)
Update jumbo_frm() (implemented in both "chain_mode.c" and "ring_mode.c")
to ensure DMA errors don't get lost due to casting the result to an
integer of the wrong size. This was a Sashiko suggestion.
In addition, add explicit calls to lower_32_bits() to DMA addresses
before they are passed to cpu_to_le32(), to guarantee the type of
the converted value is u32.
Maxime implied that a new version the first patch could handle both
fixes, but I thought it better to do them separately.
-Alex
Here is v1 of the series (the patch):
https://lore.kernel.org/lkml/20260811192703.1765416-1-elder@riscstar.com/
Alex Elder (2):
net: stmmac: use dma_addr_t for DMA addresses
net: stmmac: convert DMA address to lower 32 before assignment
drivers/net/ethernet/stmicro/stmmac/chain_mode.c | 9 +++++----
drivers/net/ethernet/stmicro/stmmac/ring_mode.c | 15 ++++++++-------
2 files changed, 13 insertions(+), 11 deletions(-)
base-commit: 5e6de6a2b522f659defacb1551d0465ba6ce13cf
--
2.53.0
next reply other threads:[~2026-08-12 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 16:38 Alex Elder [this message]
2026-08-12 16:38 ` [PATCH net-next v2 1/2] net: stmmac: use dma_addr_t for DMA addresses Alex Elder
2026-08-12 16:38 ` [PATCH net-next v2 2/2] net: stmmac: convert DMA address to lower 32 before assignment Alex Elder
2026-08-17 19:45 ` [PATCH net-next v2 0/2] net: stmmac: DMA address handling fixes patchwork-bot+netdevbpf
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=20260812163832.271742-1-elder@riscstar.com \
--to=elder@riscstar.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.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=maxime.chevallier@bootlin.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sashiko-bot@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.