From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Zhe Qiao <qiaozhe@iscas.ac.cn>
Cc: <rafael@kernel.org>, <lenb@kernel.org>, <bhelgaas@google.com>,
<will@kernel.org>, <sunilvl@ventanamicro.com>,
<linux-acpi@vger.kernel.org>, <linux-pci@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ACPI: PCI: Release excess memory usage.
Date: Tue, 29 Apr 2025 14:20:22 +0100 [thread overview]
Message-ID: <20250429142022.00003460@huawei.com> (raw)
In-Reply-To: <20250429091051.249911-1-qiaozhe@iscas.ac.cn>
On Tue, 29 Apr 2025 17:10:51 +0800
Zhe Qiao <qiaozhe@iscas.ac.cn> wrote:
> In the pci_acpi_scan_root() function, if the PCI bus creation failed,
> the allocated memory should be released to avoid memory occupation.
>
> Fixes: 789befdfa389 ("arm64: PCI: Migrate ACPI related functions to pci-acpi.c")
> Signed-off-by: Zhe Qiao <qiaozhe@iscas.ac.cn>
>
> ---
> V1 -> V2:
> Modified labels for better readability.
>
> ---
> drivers/pci/pci-acpi.c | 15 +++++++++------
> 1 file changed, 9 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/pci/pci-acpi.c b/drivers/pci/pci-acpi.c
> index af370628e583..bde104ecac80 100644
> --- a/drivers/pci/pci-acpi.c
> +++ b/drivers/pci/pci-acpi.c
> @@ -1677,15 +1677,12 @@ struct pci_bus *pci_acpi_scan_root(struct acpi_pci_root *root)
>
> root_ops = kzalloc(sizeof(*root_ops), GFP_KERNEL);
> if (!root_ops) {
> - kfree(ri);
> - return NULL;
> + goto free_ri;
> }
>
> ri->cfg = pci_acpi_setup_ecam_mapping(root);
> if (!ri->cfg) {
> - kfree(ri);
> - kfree(root_ops);
> - return NULL;
> + goto free_root_ops;
> }
>
> root_ops->release_info = pci_acpi_generic_release_info;
> @@ -1693,7 +1690,7 @@ struct pci_bus *pci_acpi_scan_root(struct acpi_pci_root *root)
> root_ops->pci_ops = (struct pci_ops *)&ri->cfg->ops->pci_ops;
> bus = acpi_pci_root_create(root, root_ops, &ri->common, ri->cfg);
> if (!bus)
> - return NULL;
Do we also need to tear down the ecam mapping done in pci_acpi_setup_ecam_mapping()?
Might just be pci_ecam_free(ri->cfg);
> + goto free_root_ops;
>
> /* If we must preserve the resource configuration, claim now */
> host = pci_find_host_bridge(bus);
> @@ -1710,6 +1707,12 @@ struct pci_bus *pci_acpi_scan_root(struct acpi_pci_root *root)
> pcie_bus_configure_settings(child);
>
> return bus;
> +
> +free_root_ops:
> + kfree(root_ops);
> +free_ri:
> + kfree(ri);
> + return NULL;
> }
>
> void pcibios_add_bus(struct pci_bus *bus)
next prev parent reply other threads:[~2025-04-29 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 9:10 [PATCH v2] ACPI: PCI: Release excess memory usage Zhe Qiao
2025-04-29 13:20 ` Jonathan Cameron [this message]
2025-04-29 15:46 ` Markus Elfring
2025-04-29 15:56 ` Markus Elfring
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=20250429142022.00003460@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=bhelgaas@google.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=qiaozhe@iscas.ac.cn \
--cc=rafael@kernel.org \
--cc=sunilvl@ventanamicro.com \
--cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.