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: <2215082.irdbgypaU6@rjwysocki.net>
Date: Fri, 04 Oct 2024 21:01:34 +0200
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Linux PM <linux-pm@...r.kernel.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
 Daniel Lezcano <daniel.lezcano@...aro.org>,
 Lukasz Luba <lukasz.luba@....com>, Zhang Rui <rui.zhang@...el.com>,
 Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>
Subject: [PATCH v2 00/12] thermal: core: Fixes and cleanups,
 mostly related to thermal zone init and exit

Hi Everyone,

After posting the two series of thermal core patches for 6.13:

https://lore.kernel.org/linux-pm/4920970.GXAFRqVoOG@rjwysocki.net/

and

https://lore.kernel.org/linux-pm/6100907.lOV4Wx5bFT@rjwysocki.net/

before the 6.12 merge window, I have decided to reorder the changes included in
these series, so that fixes and more significant cleanups (for example, changing
they layout of data structures) go first, followed by the changes related to
using guards for locking, and the optimization involving sorted lists becomes
the last piece.

This series is the first part and the majority of patches in it come from the
second (RFC) series mentioned above.  Of course, they needed to be rebased to
be applied in the new order.  It is on top of 6.12-rc1 with

https://lore.kernel.org/linux-pm/12549318.O9o76ZdvQC@rjwysocki.net/

applied and it will be added to my thermal-core-testing branch.  It is in v2
to start with because all of the patches in it have already been posted in
some form.

The first 10 patches fix some potential issues related to thermal zone
initialization and exit (for example, user space may start to interact with
a thermal zone during its initialization before it's ready and system suspend
taking place at a wrong time may skip a new thermal zone so it is not suspended)
and do some cleanups related to that.  This concludes with the removal of the
need_update field from struct thermal_zone_device.

The last two patches move lists of thermal instances from thermal zones to
trip point descriptors and clean up some code on top of that.

Please refer to the individual patch changelogs for details.

Thanks!




Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ