[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<173388723251.1105799.6013882460430110390.git-patchwork-notify@kernel.org>
Date: Wed, 11 Dec 2024 03:20:32 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Nikita Yushchenko <nikita.yoush@...entembedded.com>
Cc: yoshihiro.shimoda.uh@...esas.com, andrew@...n.ch, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
geert+renesas@...der.be, netdev@...r.kernel.org,
linux-renesas-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
michael.dege@...esas.com, christian.mardmoeller@...esas.com,
dennis.ostermann@...esas.com
Subject: Re: [PATCH net] net: renesas: rswitch: handle stop vs interrupt race
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Mon, 9 Dec 2024 16:32:04 +0500 you wrote:
> Currently the stop routine of rswitch driver does not immediately
> prevent hardware from continuing to update descriptors and requesting
> interrupts.
>
> It can happen that when rswitch_stop() executes the masking of
> interrupts from the queues of the port being closed, napi poll for
> that port is already scheduled or running on a different CPU. When
> execution of this napi poll completes, it will unmask the interrupts.
> And unmasked interrupt can fire after rswitch_stop() returns from
> napi_disable() call. Then, the handler won't mask it, because
> napi_schedule_prep() will return false, and interrupt storm will
> happen.
>
> [...]
Here is the summary with links:
- [net] net: renesas: rswitch: handle stop vs interrupt race
https://git.kernel.org/netdev/net/c/3dd002f20098
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists