linux-kernel - [PATCH v1 0/2] thermal: core: Fix two issues related to thermal zone resume

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: <6070114.lOV4Wx5bFT@kreacher>
Date: Fri, 14 Jun 2024 17:17:35 +0200
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Linux PM <linux-pm@...r.kernel.org>
Cc: Daniel Lezcano <daniel.lezcano@...aro.org>,
 LKML <linux-kernel@...r.kernel.org>, Lukasz Luba <lukasz.luba@....com>,
 Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
 Zhang Rui <rui.zhang@...el.com>
Subject:
 [PATCH v1 0/2] thermal: core: Fix two issues related to thermal zone resume

Hi Everyone,

There are two issues resulting from asynchronous suspend of thermal zones.

One of them is platform-specific and related to some firmware issue (I think)
causing battery readings to become invalid after a system resume due to
interference between ACPI battery resume and a thermal zone update.  This
can be addressed by running the thermal PM notifier after all of the other
PM notifiers (including the ACPI battery one) which is done by patch [2/2].

The other one is mostly theoretical, but I couldn't convince myself that it
cannot happen.  Namely, a leftover thermal zone resume running during the
next system suspend (if it is carried out back-to-back with the previous
suspend-resume cycle) can accidentally reset tz->suspended set for a thermal
zone by the thermal pre-suspend PM notifier.  This is addressed by patch
[1/2] (which goes before the second one because the latter increases the
likelihood of the issue slightly).

Thanks!