From: patchwork-bot+netdevbpf@kernel.org
To: Fan Wu <fanwu01@zju.edu.cn>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, andrew+netdev@lunn.ch,
stable@vger.kernel.org
Subject: Re: [PATCH v2 net] net: ethernet: arc: emac: quiesce interrupts before requesting IRQ
Date: Wed, 11 Mar 2026 02:20:06 +0000 [thread overview]
Message-ID: <177319560655.3008927.17970986810014027433.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260309132409.584966-1-fanwu01@zju.edu.cn>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 9 Mar 2026 13:24:09 +0000 you wrote:
> Normal RX/TX interrupts are enabled later, in arc_emac_open(), so probe
> should not see interrupt delivery in the usual case. However, hardware may
> still present stale or latched interrupt status left by firmware or the
> bootloader.
>
> If probe later unwinds after devm_request_irq() has installed the handler,
> such a stale interrupt can still reach arc_emac_intr() during teardown and
> race with release of the associated net_device.
>
> [...]
Here is the summary with links:
- [v2,net] net: ethernet: arc: emac: quiesce interrupts before requesting IRQ
https://git.kernel.org/netdev/net/c/2503d08f8a2d
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-03-11 2:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 13:24 [PATCH v2 net] net: ethernet: arc: emac: quiesce interrupts before requesting IRQ Fan Wu
2026-03-11 2: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=177319560655.3008927.17970986810014027433.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fanwu01@zju.edu.cn \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@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