From: Bjorn Helgaas <helgaas@kernel.org>
To: Jinhui Guo <guojinhui.liam@bytedance.com>
Cc: bhelgaas@google.com, dan.j.williams@intel.com,
dave.jiang@intel.com, ilpo.jarvinen@linux.intel.com,
kbusch@kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, stable@vger.kernel.org,
Keith Busch <kbusch@meta.com>, Alex Williamson <alex@shazbot.org>,
Lukas Wunner <lukas@wunner.de>
Subject: Re: [RESEND PATCH v2] PCI: Fix incorrect unlocking in pci_slot_trylock()
Date: Wed, 28 Jan 2026 16:53:44 -0600 [thread overview]
Message-ID: <20260128225344.GA422463@bhelgaas> (raw)
In-Reply-To: <20251212145528.2555-1-guojinhui.liam@bytedance.com>
[+cc Keith, Alex, Lukas]
On Fri, Dec 12, 2025 at 10:55:28PM +0800, Jinhui Guo wrote:
> Commit a4e772898f8b ("PCI: Add missing bridge lock to pci_bus_lock()")
> delegates the bridge device's pci_dev_trylock() to pci_bus_trylock() in
> pci_slot_trylock(), but it forgets to remove the corresponding
> pci_dev_unlock() when pci_bus_trylock() fails.
>
> Before the commit, the code did:
>
> if (!pci_dev_trylock(dev)) /* <- lock bridge device */
> goto unlock;
> if (dev->subordinate) {
> if (!pci_bus_trylock(dev->subordinate)) {
> pci_dev_unlock(dev); /* <- unlock bridge device */
> goto unlock;
> }
> }
>
> After the commit the bridge-device lock is no longer taken, but the
> pci_dev_unlock(dev) on the failure path was left in place, leading to
> the bug.
>
> This yields one of two errors:
> 1. A warning that the lock is being unlocked when no one holds it.
> 2. An incorrect unlock of a lock that belongs to another thread.
>
> Fix it by removing the now-redundant pci_dev_unlock(dev) on the failure
> path.
>
> Fixes: a4e772898f8b ("PCI: Add missing bridge lock to pci_bus_lock()")
> Cc: stable@vger.kernel.org
> Signed-off-by: Jinhui Guo <guojinhui.liam@bytedance.com>
Applied to pci/virtualization for v6.20, thanks!
> ---
>
> Hi, all
>
> Resent v2 to drop the Acked-by tag; no code changes. Sorry for the noise again.
>
> v1: https://lore.kernel.org/all/20251211123635.2215-1-guojinhui.liam@bytedance.com/
>
> Changelog in v1 -> v2
> - The v1 commit message was too brief, so I’ve sent v2 with more detail.
> - Remove the braces from the if (!pci_bus_trylock(dev->subordinate)) statement.
>
> Best Regards,
> Jinhui
>
> drivers/pci/pci.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
> index 13dbb405dc31..59319e08fca6 100644
> --- a/drivers/pci/pci.c
> +++ b/drivers/pci/pci.c
> @@ -5346,10 +5346,8 @@ static int pci_slot_trylock(struct pci_slot *slot)
> if (!dev->slot || dev->slot != slot)
> continue;
> if (dev->subordinate) {
> - if (!pci_bus_trylock(dev->subordinate)) {
> - pci_dev_unlock(dev);
> + if (!pci_bus_trylock(dev->subordinate))
> goto unlock;
> - }
> } else if (!pci_dev_trylock(dev))
> goto unlock;
> }
> --
> 2.20.1
prev parent reply other threads:[~2026-01-28 22:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 13:37 [PATCH v2] PCI: Fix incorrect unlocking in pci_slot_trylock() Jinhui Guo
2025-12-12 14:31 ` Ilpo Järvinen
2025-12-12 14:55 ` [RESEND PATCH " Jinhui Guo
2026-01-28 21:03 ` dan.j.williams
2026-01-28 22:53 ` Bjorn Helgaas [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=20260128225344.GA422463@bhelgaas \
--to=helgaas@kernel.org \
--cc=alex@shazbot.org \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=guojinhui.liam@bytedance.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=stable@vger.kernel.org \
/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