From: "Nazle Asmade, Muhammad Nazim Amirul" <muhammad.nazim.amirul.nazle.asmade@altera.com>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>,
netdev@vger.kernel.org
Cc: ansuelsmth@gmail.com, kuba@kernel.org, pabeni@redhat.com,
ast@kernel.org, daniel@iogearbox.net, bpf@vger.kernel.org
Subject: Re: [PATCH net] net: stmmac: Disable queues before netif_tx_disable in xdp_release
Date: Thu, 24 Sep 2026 10:17:15 +0800 [thread overview]
Message-ID: <47f7d038-3e14-45b3-be72-68c12e64dc19@altera.com> (raw)
In-Reply-To: <1e258c0f-8663-4dfe-a0aa-7c8be67d6afe@bootlin.com>
On 27/7/2026 4:00 pm, Maxime Chevallier wrote:
> Hi,
>
> On 7/27/26 05:06, muhammad.nazim.amirul.nazle.asmade@altera.com wrote:
>> From: Nazim Amirul <muhammad.nazim.amirul.nazle.asmade@altera.com>
>>
>> stmmac_xdp_release() calls netif_tx_disable() before
>> stmmac_disable_all_queues(), which creates a race window where NAPI
>> is still running while TX is being disabled. If a packet is still
>> queued at that point, it can be processed after TX is stopped,
>> leading to a kernel panic.
>>
>> Fix this by calling stmmac_disable_all_queues() first to stop NAPI
>> processing before disabling TX, matching the order already used in
>> stmmac_release() since 7028471edb64.
>>
>> Fixes: 7028471edb64 ("net: ethernet: stmicro: stmmac: first disable all queues and disconnect in release")
>> Signed-off-by: Rohan G Thomas <rohan.g.thomas@altera.com>
>> Signed-off-by: Nazim Amirul <muhammad.nazim.amirul.nazle.asmade@altera.com>
> Reviewed-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
>
> Maxime
Hi Jakub,
Is this patch good to merge or require any attention on my end, please
let me know if any :)
BR,
Nazim
next prev parent reply other threads:[~2026-09-24 2:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 3:06 [PATCH net] net: stmmac: Disable queues before netif_tx_disable in xdp_release muhammad.nazim.amirul.nazle.asmade
2026-07-27 8:00 ` Maxime Chevallier
2026-09-24 2:17 ` Nazle Asmade, Muhammad Nazim Amirul [this message]
2026-09-24 14:56 ` Jakub Kicinski
2026-07-30 0:56 ` 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=47f7d038-3e14-45b3-be72-68c12e64dc19@altera.com \
--to=muhammad.nazim.amirul.nazle.asmade@altera.com \
--cc=ansuelsmth@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kuba@kernel.org \
--cc=maxime.chevallier@bootlin.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