linux-kernel - [PATCH 0/2] cpufreq: Avoid checking governor return values that are always 0

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

Message-ID: <4540082.RMPf3KxPDh@vostro.rjw.lan>
Date:	Thu, 12 May 2016 15:12:54 +0200
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Linux PM list <linux-pm@...r.kernel.org>
Cc:	Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
	Viresh Kumar <viresh.kumar@...aro.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: [PATCH 0/2] cpufreq: Avoid checking governor return values that are always 0

Hi,

As it turns out, all of the existing governors (and the upcoming schedutil one)
always return 0 from ->governor() for the event argument equal to _GOV_STOP
or _POLICY_EXIT.

The following two patches rearrange the core cpufreq code to take that into
account.

Thanks,
Rafael