From: patchwork-bot+netdevbpf@kernel.org
To: Guenter Roeck <linux@roeck-us.net>
Cc: ioana.ciornei@nxp.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, moonafterrain@outlook.com
Subject: Re: [PATCH] dpaa2-switch: Fix interrupt storm after receiving bad if_id in IRQ handler
Date: Sat, 28 Feb 2026 17:20:06 +0000 [thread overview]
Message-ID: <177229920630.3019354.11284025791830317467.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260227055812.1777915-1-linux@roeck-us.net>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 26 Feb 2026 21:58:12 -0800 you wrote:
> Commit 31a7a0bbeb00 ("dpaa2-switch: add bounds check for if_id in IRQ
> handler") introduces a range check for if_id to avoid an out-of-bounds
> access. If an out-of-bounds if_id is detected, the interrupt status is
> not cleared. This may result in an interrupt storm.
>
> Clear the interrupt status after detecting an out-of-bounds if_id to avoid
> the problem.
>
> [...]
Here is the summary with links:
- dpaa2-switch: Fix interrupt storm after receiving bad if_id in IRQ handler
https://git.kernel.org/netdev/net/c/74badb9c20b1
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-02-28 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 5:58 [PATCH] dpaa2-switch: Fix interrupt storm after receiving bad if_id in IRQ handler Guenter Roeck
2026-02-27 12:40 ` Ioana Ciornei
2026-02-28 17: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=177229920630.3019354.11284025791830317467.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=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=moonafterrain@outlook.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