From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Johan Hovold <johan+linaro@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Manivannan Sadhasivam <mani@kernel.org>,
<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>
Subject: Re: [PATCH 1/3] PCI/pwrctrl: Fix device leak at registration
Date: Tue, 22 Jul 2025 11:05:26 +0100 [thread overview]
Message-ID: <20250722110526.00002a60@huawei.com> (raw)
In-Reply-To: <20250721153609.8611-2-johan+linaro@kernel.org>
On Mon, 21 Jul 2025 17:36:07 +0200
Johan Hovold <johan+linaro@kernel.org> wrote:
> Make sure to drop the reference to the pwrctrl device taken by
> of_find_device_by_node() when registering a PCI device.
>
> Fixes: b458ff7e8176 ("PCI/pwrctl: Ensure that pwrctl drivers are probed before PCI client drivers")
> Cc: stable@vger.kernel.org # 6.13
> Cc: Manivannan Sadhasivam <mani@kernel.org>
> Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
Hi Johan,
Perhaps time for
DEFINE_FREE(put_pdev, struct platform_device *, if (_T) put_device(&_T->dev));
then...
> ---
> drivers/pci/bus.c | 14 +++++++++-----
> 1 file changed, 9 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/pci/bus.c b/drivers/pci/bus.c
> index 69048869ef1c..0394a9c77b38 100644
> --- a/drivers/pci/bus.c
> +++ b/drivers/pci/bus.c
> @@ -362,11 +362,15 @@ void pci_bus_add_device(struct pci_dev *dev)
> * before PCI client drivers.
> */
> pdev = of_find_device_by_node(dn);
> - if (pdev && of_pci_supply_present(dn)) {
> - if (!device_link_add(&dev->dev, &pdev->dev,
> - DL_FLAG_AUTOREMOVE_CONSUMER))
> - pci_err(dev, "failed to add device link to power control device %s\n",
> - pdev->name);
struct platform_device *pdev __free(put_pdev) =
of_find_device_by_node(dn);
> + if (pdev) {
> + if (of_pci_supply_present(dn)) {
> + if (!device_link_add(&dev->dev, &pdev->dev,
> + DL_FLAG_AUTOREMOVE_CONSUMER)) {
> + pci_err(dev, "failed to add device link to power control device %s\n",
> + pdev->name);
> + }
> + }
> + put_device(&pdev->dev);
and no need for any explicit put.
We already do this extensively in some subsystems (e.g. CXL) and it
greatly simplifies code.
> }
>
> if (!dn || of_device_is_available(dn))
next prev parent reply other threads:[~2025-07-22 10:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250721153609.8611-1-johan+linaro@kernel.org>
2025-07-21 15:36 ` [PATCH 1/3] PCI/pwrctrl: Fix device leak at registration Johan Hovold
2025-07-22 10:05 ` Jonathan Cameron [this message]
2025-07-22 12:00 ` Johan Hovold
2025-07-22 18:33 ` Markus Elfring
2025-07-21 15:36 ` [PATCH 2/3] PCI/pwrctrl: Fix device and OF node leak at bus scan Johan Hovold
2025-07-22 10:08 ` Jonathan Cameron
2025-07-22 12:04 ` Johan Hovold
2025-07-21 15:36 ` [PATCH 3/3] PCI/pwrctrl: Fix device leak at device stop Johan Hovold
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=20250722110526.00002a60@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=bhelgaas@google.com \
--cc=johan+linaro@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mani@kernel.org \
--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