[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <176835971846.41689.7422242896755052198.b4-ty@linux.ibm.com>
Date: Wed, 14 Jan 2026 08:34:20 +0530
From: Madhavan Srinivasan <maddy@...ux.ibm.com>
To: mahesh@...ux.ibm.com, oohall@...il.com, mpe@...erman.id.au,
npiggin@...il.com, Christophe Leroy <chleroy@...nel.org>,
Narayana Murty N <nnmlinux@...ux.ibm.com>
Cc: bhelgaas@...gle.com, tpearson@...torengineering.com,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
vaibhav@...ux.ibm.com, sbhat@...ux.ibm.com, ganeshgr@...ux.ibm.com
Subject: Re: [PATCH v2 1/1] powerpc/eeh: fix recursive pci_lock_rescan_remove locking in EEH event handling
On Wed, 10 Dec 2025 08:25:59 -0600, Narayana Murty N wrote:
> The recent commit 1010b4c012b0 ("powerpc/eeh: Make EEH driver device
> hotplug safe") restructured the EEH driver to improve synchronization
> with the PCI hotplug layer.
>
> However, it inadvertently moved pci_lock_rescan_remove() outside its
> intended scope in eeh_handle_normal_event(), leading to broken PCI
> error reporting and improper EEH event triggering. Specifically,
> eeh_handle_normal_event() acquired pci_lock_rescan_remove() before
> calling eeh_pe_bus_get(), but eeh_pe_bus_get() itself attempts to
> acquire the same lock internally, causing nested locking and disrupting
> normal EEH event handling paths.
>
> [...]
Applied to powerpc/next.
[1/1] powerpc/eeh: fix recursive pci_lock_rescan_remove locking in EEH event handling
https://git.kernel.org/powerpc/c/815a8d2feb5615ae7f0b5befd206af0b0160614c
cheers
Powered by blists - more mailing lists