From: patchwork-bot+netdevbpf@kernel.org
To: ZhaoJinming <zhaojinming@uniontech.com>
Cc: netdev@vger.kernel.org, maxime.chevallier@bootlin.com,
andrew@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, boon.leong.ong@intel.com,
weifeng.voon@intel.com, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, joabreu@synopsys.com,
f.fainelli@gmail.com
Subject: Re: [PATCH] net: stmmac: stop DMA before freeing descriptors on open
Date: Tue, 01 Sep 2026 00:20:14 +0000 [thread overview]
Message-ID: <178822201413.848040.18166339908544983659.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <32EB352EB66D74E7+20260827025415.2684733-1-zhaojinming@uniontech.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 27 Aug 2026 10:54:15 +0800 you wrote:
> In __stmmac_open() and stmmac_xdp_open(), the DMA engine is started
> before stmmac_request_irq() is called. If the IRQ request fails, the
> clean-up paths free the DMA descriptor rings via dma_free_coherent()
> without stopping the DMA engine first.
>
> With the DMA engine still running, hardware may continue to access the
> descriptor ring memory after it has been freed. Add stmmac_stop_all_dma()
> to both error paths, matching the teardown order in __stmmac_release().
>
> [...]
Here is the summary with links:
- net: stmmac: stop DMA before freeing descriptors on open
https://git.kernel.org/netdev/net-next/c/25c1f6111034
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-01 0:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 2:54 [PATCH] net: stmmac: stop DMA before freeing descriptors on open ZhaoJinming
2026-09-01 0:20 ` patchwork-bot+netdevbpf [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=178822201413.848040.18166339908544983659.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew@lunn.ch \
--cc=boon.leong.ong@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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=weifeng.voon@intel.com \
--cc=zhaojinming@uniontech.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