From: Lukas Wunner <lukas@wunner.de>
To: Mario Limonciello <superm1@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
"open list:PCI SUBSYSTEM" <linux-pci@vger.kernel.org>,
linux-pm@vger.kernel.org,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Mario Limonciello <mario.limonciello@amd.com>
Subject: Re: [PATCH v3 2/2] PCI: Fix runtime PM usage count underflow on device unplug
Date: Mon, 23 Jun 2025 08:43:25 +0200 [thread overview]
Message-ID: <aFj3jUAM42lSyfpe@wunner.de> (raw)
In-Reply-To: <295bf182-7fed-4ffd-93a4-fb5ddf5f1bb4@kernel.org>
On Sun, Jun 22, 2025 at 01:39:26PM -0500, Mario Limonciello wrote:
> > > On 6/21/25 2:05 PM, Lukas Wunner wrote:
> > > > So the refcount decrement happens in pcie_portdrv_probe() and
> > > > the refcount increment happens in pcie_portdrv_remove().
> > > > Both times it's conditional on pci_bridge_d3_possible().
> > > > Does that return a different value on probe versus remove?
>
> I did this check and yes specifically on this PCIe port with the underflow
> the d3 possible lookup returns false during pcie_portdrv_remove(). It
> returns true during pcie_portdrv_probe().
That's not supposed to happen. The expectation is that
pci_bridge_d3_possible() always returns the same value.
For this reason the return value on ->probe() isn't cached.
So which of the conditions changes in pci_bridge_d3_possible()
on probe versus remove? Could you instrument each with a printk()
so that we can understand what's going wrong there?
Thanks,
Lukas
next prev parent reply other threads:[~2025-06-23 6:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 2:55 [PATCH v3 0/2] Don't make noise about disconnected USB4 devices Mario Limonciello
2025-06-20 2:55 ` [PATCH v3 1/2] PCI/PM: Skip resuming to D0 if disconnected Mario Limonciello
2025-06-23 17:48 ` Lukas Wunner
2025-06-20 2:55 ` [PATCH v3 2/2] PCI: Fix runtime PM usage count underflow on device unplug Mario Limonciello
2025-06-21 19:05 ` Lukas Wunner
2025-06-21 19:56 ` Mario Limonciello
2025-06-22 4:43 ` Lukas Wunner
2025-06-22 18:39 ` Mario Limonciello
2025-06-23 1:47 ` Mario Limonciello
2025-06-23 6:53 ` Lukas Wunner
2025-06-23 6:43 ` Lukas Wunner [this message]
2025-06-23 7:37 ` Lukas Wunner
2025-06-23 10:05 ` Lukas Wunner
2025-06-23 10:11 ` Rafael J. Wysocki
2025-06-23 11:37 ` Mario Limonciello
2025-06-23 12:19 ` Lukas Wunner
2025-06-23 12:45 ` Mario Limonciello
2025-06-23 17:23 ` Lukas Wunner
2025-06-23 17:25 ` Mario Limonciello
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=aFj3jUAM42lSyfpe@wunner.de \
--to=lukas@wunner.de \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=rjw@rjwysocki.net \
--cc=superm1@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;
as well as URLs for NNTP newsgroup(s).