summaryrefslogtreecommitdiff
path: root/include/linux
diff options
context:
space:
mode:
authorSrinivas Pandruvada <srinivas.pandruvada@intel.com>2023-03-03 08:19:09 -0800
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2023-03-03 20:34:49 +0100
commit52f04f10b9005ac4ce640da14a52ed7a146432fa (patch)
tree84aafa1459373c291ff0d9909418460a0454f4af /include/linux
parent0a3f9a6b0265b64c02226fcabb5e9a958307913b (diff)
downloadlwn-52f04f10b9005ac4ce640da14a52ed7a146432fa.tar.gz
lwn-52f04f10b9005ac4ce640da14a52ed7a146432fa.zip
thermal: intel: int340x: processor_thermal: Fix deadlock
When user space updates the trip point there is a deadlock, which results in caller gets blocked forever. Commit 05eeee2b51b4 ("thermal/core: Protect sysfs accesses to thermal operations with thermal zone mutex"), added a mutex for tz->lock in the function trip_point_temp_store(). Hence, trip set callback() can't call any thermal zone API as they are protected with the same mutex lock. The callback here calling thermal_zone_device_enable(), which will result in deadlock. Move the thermal_zone_device_enable() to proc_thermal_pci_probe() to avoid this deadlock. Fixes: 05eeee2b51b4 ("thermal/core: Protect sysfs accesses to thermal operations with thermal zone mutex") Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@intel.com> Cc: 6.2+ <stable@vger.kernel.org> # 6.2+ Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions