Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: "Wysocki, Rafael J" <rafael.j.wysocki@intel.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
	stable@vger.kernel.org
Cc: Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: [PATCH 6.14.y and others] cpufreq: Reference count policy in cpufreq_update_limits()
Date: Sat, 19 Apr 2025 17:31:03 +0200	[thread overview]
Message-ID: <eb74abac-074e-498b-a00e-0eb878b74251@intel.com> (raw)
In-Reply-To: <20250418021517.1960418-1-marmarek@invisiblethingslab.com>

On 4/18/2025 4:15 AM, Marek Marczykowski-Górecki wrote:
> From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
>
> Since acpi_processor_notify() can be called before registering a cpufreq
> driver or even in cases when a cpufreq driver is not registered at all,
> cpufreq_update_limits() needs to check if a cpufreq driver is present
> and prevent it from being unregistered.
>
> For this purpose, make it call cpufreq_cpu_get() to obtain a cpufreq
> policy pointer for the given CPU and reference count the corresponding
> policy object, if present.
>
> Fixes: 5a25e3f7cc53 ("cpufreq: intel_pstate: Driver-specific handling of _PPC updates")
> Closes: https://lore.kernel.org/linux-acpi/Z-ShAR59cTow0KcR@mail-itl
> Reported-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
> Cc: All applicable <stable@vger.kernel.org>
> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
> Link: https://patch.msgid.link/1928789.tdWV9SEqCh@rjwysocki.net
> (cherry picked from commit 9e4e249018d208678888bdf22f6b652728106528)
> [do not use __free(cpufreq_cpu_put) in a backport]
> Signed-off-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
> ---
> This patch is applicable to other stable branches too.

Thanks a lot for taking care of backporting it!


> ---
>   drivers/cpufreq/cpufreq.c | 8 ++++++++
>   1 file changed, 8 insertions(+)
>
> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> index 30ffbddc7ece..934e0e19824c 100644
> --- a/drivers/cpufreq/cpufreq.c
> +++ b/drivers/cpufreq/cpufreq.c
> @@ -2762,10 +2762,18 @@ EXPORT_SYMBOL(cpufreq_update_policy);
>    */
>   void cpufreq_update_limits(unsigned int cpu)
>   {
> +	struct cpufreq_policy *policy;
> +
> +	policy = cpufreq_cpu_get(cpu);
> +	if (!policy)
> +		return;
> +
>   	if (cpufreq_driver->update_limits)
>   		cpufreq_driver->update_limits(cpu);
>   	else
>   		cpufreq_update_policy(cpu);
> +
> +	cpufreq_cpu_put(policy);
>   }
>   EXPORT_SYMBOL_GPL(cpufreq_update_limits);
>   

      parent reply	other threads:[~2025-04-19 15:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17 13:28 FAILED: patch "[PATCH] cpufreq: Reference count policy in cpufreq_update_limits()" failed to apply to 6.14-stable tree gregkh
2025-04-17 23:52 ` Marek Marczykowski-Górecki
2025-04-18  1:51   ` Marek Marczykowski-Górecki
2025-04-18  2:15 ` [PATCH 6.14.y and others] cpufreq: Reference count policy in cpufreq_update_limits() Marek Marczykowski-Górecki
2025-04-19 11:50   ` Sasha Levin
2025-04-19 15:31   ` Wysocki, Rafael J [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=eb74abac-074e-498b-a00e-0eb878b74251@intel.com \
    --to=rafael.j.wysocki@intel.com \
    --cc=marmarek@invisiblethingslab.com \
    --cc=stable@vger.kernel.org \
    --cc=viresh.kumar@linaro.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