linux-kernel - Re: [PATCH] cpufreq: Fixed kernel crash caused by cpufreq issues

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date: Fri, 12 Apr 2024 13:26:07 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Lizhe <sensor1010@....com>
Cc: rafael@...nel.org, viresh.kumar@...aro.org, linux-pm@...r.kernel.org, 
	linux-kernel@...r.kernel.org, Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH] cpufreq: Fixed kernel crash caused by cpufreq issues

On Fri, Apr 12, 2024 at 1:19 AM Lizhe <sensor1010@....com> wrote:
>
> When the cpufreq_driver does not provide an exit() function.
> cpufreq offline operations can result in a kernel crash.
>
> Signed-off-by: Lizhe <sensor1010@....com>
> ---
>  drivers/cpufreq/cpufreq.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> index 04d349372de3..e8660bc7d232 100644
> --- a/drivers/cpufreq/cpufreq.c
> +++ b/drivers/cpufreq/cpufreq.c
> @@ -1739,7 +1739,7 @@ static void cpufreq_remove_dev(struct device *dev, struct subsys_interface *sif)
>         }
>
>         /* We did light-weight exit earlier, do full tear down now */
> -       if (cpufreq_driver->offline)
> +       if (cpufreq_driver->offline && cpufreq_driver->exit)
>                 cpufreq_driver->exit(policy);
>
>         up_write(&policy->rwsem);
> --

I've applied the patch from Viresh that addresses both issues with
missing ->exit() driver callback checks and therefore is more
complete.

Also I'm not going to apply any other patches you have sent because
there were obvious mistakes in some of them and you sent updates
without version numbering and without any information regarding what
changed with respect to the previous version(s).  Also some patches
were sent in multiple copies (I think) without telling me which one to
look at.  All of that is too confusing to be treated seriously and
quite disrespectful to the prospective reviewers (who might allocate
their time to more productive things).

If you want to send the changes once again, it is fine because they
generally do some nice cleanups, but please follow the patch
submission and kernel development process documentation as Greg has
already advised you.

Thanks!