From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Ma Ke <make24@iscas.ac.cn>
Cc: bhelgaas@google.com, yinghai@kernel.org,
rafael.j.wysocki@intel.com, akpm@linux-foundation.org,
linux-pci@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH v2 RESEND] PCI: fix reference leak in pci_alloc_child_bus()
Date: Fri, 24 Jan 2025 11:19:33 +0200 (EET) [thread overview]
Message-ID: <46c252b0-880c-aca1-f6e5-c78ebe28a7a0@linux.intel.com> (raw)
In-Reply-To: <20250119070550.2278800-1-make24@iscas.ac.cn>
On Sun, 19 Jan 2025, Ma Ke wrote:
> When device_register(&child->dev) failed, calling put_device() to
> explicitly release child->dev. Otherwise, it could cause double free
> problem.
While the code fix seem okay, this double free part in the problem
description isn't. The reference is held w/o this fix so it's not getting
freed at all, let alone freed twice.
> device_register() includes device_add(). As comment of device_add()
> says, 'if device_add() succeeds, you should call device_del() when you
> want to get rid of it. If device_add() has not succeeded, use only
> put_device() to drop the reference count'.
>
> Found by code review.
>
> Cc: stable@vger.kernel.org
> Fixes: 4f535093cf8f ("PCI: Put pci_dev in device tree as early as possible")
> Signed-off-by: Ma Ke <make24@iscas.ac.cn>
> ---
> Changes in v2:
> - added the bug description about the comment of device_add();
> - fixed the patch as suggestions;
> - added Cc and Fixes table.
> ---
> drivers/pci/probe.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
> index 2e81ab0f5a25..ae12f92c6a9d 100644
> --- a/drivers/pci/probe.c
> +++ b/drivers/pci/probe.c
> @@ -1174,7 +1174,10 @@ static struct pci_bus *pci_alloc_child_bus(struct pci_bus *parent,
> add_dev:
> pci_set_bus_msi_domain(child);
> ret = device_register(&child->dev);
> - WARN_ON(ret < 0);
> + if (WARN_ON(ret < 0)) {
> + put_device(&child->dev);
> + return NULL;
> + }
>
> pcibios_add_bus(child);
>
>
--
i.
prev parent reply other threads:[~2025-01-24 9:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-19 7:05 Ma Ke
2025-01-24 9:19 ` Ilpo Järvinen [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=46c252b0-880c-aca1-f6e5-c78ebe28a7a0@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=make24@iscas.ac.cn \
--cc=rafael.j.wysocki@intel.com \
--cc=stable@vger.kernel.org \
--cc=yinghai@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
all inboxes | Powered by JetHome®