From: Shuai Xue <xueshuai@linux.alibaba.com>
To: Yunhui Cui <cuiyunhui@bytedance.com>,
renyu.zj@linux.alibaba.com, will@kernel.org,
mark.rutland@arm.com, linux-arm-kernel@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] perf/dwc_pcie: fix some unreleased resources
Date: Mon, 24 Feb 2025 09:52:55 +0800 [thread overview]
Message-ID: <f532b261-631f-41ac-813e-cb351eb1f8f3@linux.alibaba.com> (raw)
In-Reply-To: <20250220121716.50324-2-cuiyunhui@bytedance.com>
在 2025/2/20 20:17, Yunhui Cui 写道:
> Release leaked resources, such as plat_dev and dev_info.
>
> Signed-off-by: Yunhui Cui <cuiyunhui@bytedance.com>
> ---
> drivers/perf/dwc_pcie_pmu.c | 33 ++++++++++++++++++++++-----------
> 1 file changed, 22 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/perf/dwc_pcie_pmu.c b/drivers/perf/dwc_pcie_pmu.c
> index cccecae9823f..19fa2ba8dd67 100644
> --- a/drivers/perf/dwc_pcie_pmu.c
> +++ b/drivers/perf/dwc_pcie_pmu.c
> @@ -572,8 +572,10 @@ static int dwc_pcie_register_dev(struct pci_dev *pdev)
> return PTR_ERR(plat_dev);
>
> dev_info = kzalloc(sizeof(*dev_info), GFP_KERNEL);
> - if (!dev_info)
> + if (!dev_info) {
> + platform_device_unregister(plat_dev);
> return -ENOMEM;
> + }
>
> /* Cache platform device to handle pci device hotplug */
> dev_info->plat_dev = plat_dev;
> @@ -730,6 +732,15 @@ static struct platform_driver dwc_pcie_pmu_driver = {
> .driver = {.name = "dwc_pcie_pmu",},
> };
>
> +static void dwc_pcie_cleanup_devices(void)
> +{
> + struct dwc_pcie_dev_info *dev_info, *tmp;
> +
> + list_for_each_entry_safe(dev_info, tmp, &dwc_pcie_dev_info_head, dev_node) {
> + dwc_pcie_unregister_dev(dev_info);
> + }
> +}
> +
> static int __init dwc_pcie_pmu_init(void)
> {
> struct pci_dev *pdev = NULL;
> @@ -742,7 +753,7 @@ static int __init dwc_pcie_pmu_init(void)
> ret = dwc_pcie_register_dev(pdev);
> if (ret) {
> pci_dev_put(pdev);
> - return ret;
> + goto err_cleanup;
> }
> }
>
> @@ -751,35 +762,35 @@ static int __init dwc_pcie_pmu_init(void)
> dwc_pcie_pmu_online_cpu,
> dwc_pcie_pmu_offline_cpu);
> if (ret < 0)
> - return ret;
> + goto err_cleanup;
>
> dwc_pcie_pmu_hp_state = ret;
>
> ret = platform_driver_register(&dwc_pcie_pmu_driver);
> if (ret)
> - goto platform_driver_register_err;
> + goto err_remove_cpuhp;
>
> ret = bus_register_notifier(&pci_bus_type, &dwc_pcie_pmu_nb);
> if (ret)
> - goto platform_driver_register_err;
> + goto err_unregister_driver;
> notify = true;
>
> return 0;
>
> -platform_driver_register_err:
> +err_unregister_driver:
> + platform_driver_unregister(&dwc_pcie_pmu_driver);
> +err_remove_cpuhp:
> cpuhp_remove_multi_state(dwc_pcie_pmu_hp_state);
> -
> +err_cleanup:
> + dwc_pcie_cleanup_devices();
> return ret;
> }
>
> static void __exit dwc_pcie_pmu_exit(void)
> {
> - struct dwc_pcie_dev_info *dev_info, *tmp;
> -
> if (notify)
> bus_unregister_notifier(&pci_bus_type, &dwc_pcie_pmu_nb);
> - list_for_each_entry_safe(dev_info, tmp, &dwc_pcie_dev_info_head, dev_node)
> - dwc_pcie_unregister_dev(dev_info);
> + dwc_pcie_cleanup_devices();
> platform_driver_unregister(&dwc_pcie_pmu_driver);
> cpuhp_remove_multi_state(dwc_pcie_pmu_hp_state);
> }
LGTM. Thanks.
Reviewed-by: Shuai Xue <xueshuai@linux.alibaba.com>
Shuai
next prev parent reply other threads:[~2025-02-24 1:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 12:17 [PATCH v4 0/2] Fix dwc_pcie pmu driver issues Yunhui Cui
2025-02-20 12:17 ` [PATCH v4 1/2] perf/dwc_pcie: fix some unreleased resources Yunhui Cui
2025-02-24 1:52 ` Shuai Xue [this message]
2025-02-20 12:17 ` [PATCH v4 2/2] perf/dwc_pcie: fix duplicate pci_dev devices Yunhui Cui
2025-02-24 1:54 ` Shuai Xue
2025-03-01 7:05 ` [PATCH v4 0/2] Fix dwc_pcie pmu driver issues Will Deacon
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=f532b261-631f-41ac-813e-cb351eb1f8f3@linux.alibaba.com \
--to=xueshuai@linux.alibaba.com \
--cc=cuiyunhui@bytedance.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=renyu.zj@linux.alibaba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox