linux-kernel - Re: [PATCH] acpi-cpufreq: Skip cleanup if initialization didn't occur

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20210607072637.b5mwcalab7y2vikx@vireshk-i7>
Date:   Mon, 7 Jun 2021 12:56:37 +0530
From:   Viresh Kumar <viresh.kumar@...aro.org>
To:     Takashi Iwai <tiwai@...e.de>
Cc:     kyle.meyer@....com, rjw@...ysocki.net,
        linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
        linux-acpi@...r.kernel.org, Takashi Iwai <tiwai@...e.com>
Subject: Re: [PATCH] acpi-cpufreq: Skip cleanup if initialization didn't occur

On 07-06-21, 09:13, Takashi Iwai wrote:
> The missing key information is that it's a fix for the recent change
> for 5.14, i.e. 
> Fixes: c1d6d2fd2f64 ("cpufreq: acpi-cpufreq: Skip initialization if cpufreq driver is present")
> 
> The change made the module left even if it exits before registering
> the cpufreq driver object.

The original patch looks buggy to me, I was never able to review it :(

I have replied on the original thread instead.

-- 
viresh