[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240822173810.11090-3-W_Armin@gmx.de>
Date: Thu, 22 Aug 2024 19:38:07 +0200
From: Armin Wolf <W_Armin@....de>
To: james@...iv.tech,
jlee@...e.com,
corentin.chary@...il.com,
luke@...nes.dev,
matan@...alib.org,
coproscefalo@...il.com
Cc: hdegoede@...hat.com,
ilpo.jarvinen@...ux.intel.com,
rafael@...nel.org,
lenb@...nel.org,
platform-driver-x86@...r.kernel.org,
linux-hwmon@...r.kernel.org,
linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [PATCH 2/5] hwmon: (hp-wmi-sensors) Check if WMI event data exists
The BIOS can choose to return no event data in response to a
WMI event, so the ACPI object passed to the WMI notify handler
can be NULL.
Check for such a situation and ignore the event in such a case.
Signed-off-by: Armin Wolf <W_Armin@....de>
---
drivers/hwmon/hp-wmi-sensors.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/hwmon/hp-wmi-sensors.c b/drivers/hwmon/hp-wmi-sensors.c
index 6892518d537c..d6bdad26feb1 100644
--- a/drivers/hwmon/hp-wmi-sensors.c
+++ b/drivers/hwmon/hp-wmi-sensors.c
@@ -1628,6 +1628,9 @@ static void hp_wmi_notify(union acpi_object *wobj, void *context)
* HPBIOS_BIOSEvent instance.
*/
+ if (!wobj)
+ return;
+
mutex_lock(&state->lock);
err = populate_event_from_wobj(dev, &event, wobj);
--
2.39.2
Powered by blists - more mailing lists