mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "lihuisong (C)" <lihuisong@huawei.com>
To: <rafael@kernel.org>, <lenb@kernel.org>
Cc: <linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linuxarm@huawei.com>, <jonathan.cameron@huawei.com>,
	<zhanjie9@hisilicon.com>, <zhenglifeng1@huawei.com>,
	<yubowen8@huawei.com>, <liuyonglong@huawei.com>
Subject: Re: [PATCH] ACPI: processor: idle: Fix resource rollback in acpi_processor_power_init
Date: Sat, 28 Jun 2025 08:54:34 +0800	[thread overview]
Message-ID: <99e8badc-cd1d-4a8f-a56d-6c534a18ab0f@huawei.com> (raw)
In-Reply-To: <20250619061327.1674384-1-lihuisong@huawei.com>

Kindly ping for review.

在 2025/6/19 14:13, Huisong Li 写道:
> There are two resource rollback issues in acpi_processor_power_init:
> 1> Do not unregister acpi_idle_driver when do kzalloc failed.
> 2> Do not free cpuidle device memory when register cpuidle device failed.
>
> Signed-off-by: Huisong Li <lihuisong@huawei.com>
> ---
>   drivers/acpi/processor_idle.c | 24 +++++++++++++++++-------
>   1 file changed, 17 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c
> index 2c2dc559e0f8..3548ab9dac9e 100644
> --- a/drivers/acpi/processor_idle.c
> +++ b/drivers/acpi/processor_idle.c
> @@ -1392,8 +1392,10 @@ int acpi_processor_power_init(struct acpi_processor *pr)
>   		}
>   
>   		dev = kzalloc(sizeof(*dev), GFP_KERNEL);
> -		if (!dev)
> -			return -ENOMEM;
> +		if (!dev) {
> +			retval = -ENOMEM;
> +			goto unregister_driver;
> +		}
>   		per_cpu(acpi_cpuidle_device, pr->id) = dev;
>   
>   		acpi_processor_setup_cpuidle_dev(pr, dev);
> @@ -1402,14 +1404,22 @@ int acpi_processor_power_init(struct acpi_processor *pr)
>   		 * must already be registered before registering device
>   		 */
>   		retval = cpuidle_register_device(dev);
> -		if (retval) {
> -			if (acpi_processor_registered == 0)
> -				cpuidle_unregister_driver(&acpi_idle_driver);
> -			return retval;
> -		}
> +		if (retval)
> +			goto free_cpuidle_device;
> +
>   		acpi_processor_registered++;
>   	}
>   	return 0;
> +
> +free_cpuidle_device:
> +	per_cpu(acpi_cpuidle_device, pr->id) = NULL;
> +	kfree(dev);
> +
> +unregister_driver:
> +	if (acpi_processor_registered == 0)
> +		cpuidle_unregister_driver(&acpi_idle_driver);
> +
> +	return retval;
>   }
>   
>   int acpi_processor_power_exit(struct acpi_processor *pr)

  reply	other threads:[~2025-06-28  0:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19  6:13 Huisong Li
2025-06-28  0:54 ` lihuisong (C) [this message]
2025-07-02 17:42 ` Rafael J. Wysocki
2025-07-03  6:23   ` lihuisong (C)
2025-07-03 11:09     ` Rafael J. Wysocki
2025-07-14  1:33       ` lihuisong (C)
2025-07-22 11:05         ` lihuisong (C)
2025-07-22 11:10         ` Rafael J. Wysocki
2025-07-22 11:28           ` lihuisong (C)

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=99e8badc-cd1d-4a8f-a56d-6c534a18ab0f@huawei.com \
    --to=lihuisong@huawei.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=liuyonglong@huawei.com \
    --cc=rafael@kernel.org \
    --cc=yubowen8@huawei.com \
    --cc=zhanjie9@hisilicon.com \
    --cc=zhenglifeng1@huawei.com \
    /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®