[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id:
<176485860604.800217.14018174657269207121.git-patchwork-notify@kernel.org>
Date: Thu, 04 Dec 2025 14:30:06 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Gerd Bayer <gbayer@...ux.ibm.com>
Cc: saeedm@...dia.com, leon@...nel.org, tariqt@...dia.com, mbloch@...dia.com,
andrew+netdev@...n.ch, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, shayd@...dia.com, horms@...nel.org,
lukas@...ner.de, helgaas@...nel.org, schnelle@...ux.ibm.com,
alifm@...ux.ibm.com, netdev@...r.kernel.org, linux-rdma@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-s390@...r.kernel.org,
linux-pci@...r.kernel.org
Subject: Re: [PATCH net] net/mlx5: Fix double unregister of HCA_PORTS
component
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@...hat.com>:
On Tue, 02 Dec 2025 12:12:57 +0100 you wrote:
> Clear hca_devcom_comp in device's private data after unregistering it in
> LAG teardown. Otherwise a slightly lagging second pass through
> mlx5_unload_one() might try to unregister it again and trip over
> use-after-free.
>
> On s390 almost all PCI level recovery events trigger two passes through
> mxl5_unload_one() - one through the poll_health() method and one through
> mlx5_pci_err_detected() as callback from generic PCI error recovery.
> While testing PCI error recovery paths with more kernel debug features
> enabled, this issue reproducibly led to kernel panics with the following
> call chain:
>
> [...]
Here is the summary with links:
- [net] net/mlx5: Fix double unregister of HCA_PORTS component
https://git.kernel.org/netdev/net/c/6a107cfe9c99
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