From: Niklas Schnelle <schnelle@linux.ibm.com>
To: Farhan Ali <alifm@linux.ibm.com>,
Bjorn Helgaas <helgaas@kernel.org>,
Lukas Wunner <lukas@wunner.de>
Cc: Keith Busch <kbusch@kernel.org>,
Gerd Bayer <gbayer@linux.ibm.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Benjamin Block <bblock@linux.ibm.com>,
Halil Pasic <pasic@linux.ibm.com>,
Julian Ruess <julianr@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] PCI: Add lockdep assertion in pci_stop_and_remove_bus_device()
Date: Thu, 25 Sep 2025 09:25:10 +0200 [thread overview]
Message-ID: <ac80630fda0c85ee1194ab08974aaf5f93e09cf9.camel@linux.ibm.com> (raw)
In-Reply-To: <48360cde-81d9-4161-8c32-0029e193c685@linux.ibm.com>
On Wed, 2025-09-24 at 11:06 -0700, Farhan Ali wrote:
> On 8/26/2025 1:52 AM, Niklas Schnelle wrote:
> > Removing a PCI devices requires holding pci_rescan_remove_lock. Prompted
> > by this being missed in sriov_disable() and going unnoticed since its
> > inception add a lockdep assert so this doesn't get missed again in the
> > future.
> >
> > Reviewed-by: Benjamin Block <bblock@linux.ibm.com>
> > Signed-off-by: Niklas Schnelle <schnelle@linux.ibm.com>
> > ---
> > drivers/pci/pci.h | 2 ++
> > drivers/pci/probe.c | 2 +-
> > drivers/pci/remove.c | 1 +
> > 3 files changed, 4 insertions(+), 1 deletion(-)
> >
--- snip ---
> > diff --git a/drivers/pci/remove.c b/drivers/pci/remove.c
> > index 445afdfa6498edc88f1ef89df279af1419025495..0b9a609392cecba36a818bc496a0af64061c259a 100644
> > --- a/drivers/pci/remove.c
> > +++ b/drivers/pci/remove.c
> > @@ -138,6 +138,7 @@ static void pci_remove_bus_device(struct pci_dev *dev)
> > */
> > void pci_stop_and_remove_bus_device(struct pci_dev *dev)
> > {
> > + lockdep_assert_held(&pci_rescan_remove_lock);
> > pci_stop_bus_device(dev);
> > pci_remove_bus_device(dev);
> > }
>
> We also have the function pci_stop_and_remove_bus_device_locked() as
> Gerd mentioned, so is pci_stop_and_remove_bus_device meant to be called
> without the rescan_remove_lock held? This is a little confusing as we
> shouldn't be adding/removing from the bus without the lock AFAIU, but
> maybe I am missing something?
>
> Thanks
> Farhan
As far as I understand one would use pci_stop_and_remove_bus_device()
if one is already holding the pci_rescan_remove_lock and
pci_stop_and_remove_bus_device_locked() if one only needs to take it
for that call. I think this is kind of easy to get confused about so
this lockdep assertion is even more useful.
next prev parent reply other threads:[~2025-09-25 7:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 8:52 [PATCH 0/2] PCI/IOV: Add missing PCI rescan-remove locking when enabling/disabling SR-IOV Niklas Schnelle
2025-08-26 8:52 ` [PATCH 1/2] " Niklas Schnelle
2025-09-24 17:57 ` Farhan Ali
2025-09-25 7:48 ` Niklas Schnelle
2025-09-25 22:05 ` Farhan Ali
2025-09-26 9:24 ` Julian Ruess
2025-08-26 8:52 ` [PATCH 2/2] PCI: Add lockdep assertion in pci_stop_and_remove_bus_device() Niklas Schnelle
2025-09-12 14:48 ` Gerd Bayer
2025-09-24 18:06 ` Farhan Ali
2025-09-25 7:25 ` Niklas Schnelle [this message]
2025-09-26 9:25 ` Julian Ruess
2025-09-26 21:02 ` [PATCH 0/2] PCI/IOV: Add missing PCI rescan-remove locking when enabling/disabling SR-IOV Bjorn Helgaas
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=ac80630fda0c85ee1194ab08974aaf5f93e09cf9.camel@linux.ibm.com \
--to=schnelle@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=alifm@linux.ibm.com \
--cc=bblock@linux.ibm.com \
--cc=gbayer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=helgaas@kernel.org \
--cc=julianr@linux.ibm.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mjrosato@linux.ibm.com \
--cc=pasic@linux.ibm.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