hwmon: asus_wmi_sensors: Fix info[] allocation type
Subsystems (2)
PATCH 1/1 hwmon: asus_wmi_sensors: Fix info[] allocation type
From: Kees Cook <[email protected]>
In preparation for making the devm_kmalloc family of allocators type aware, we need to make sure that the returned type from the allocation matches the type of the variable being assigned. (Before, the allocator would always return "void *", which can be implicitly cast to any pointer type.)
The assigned type of "sensor_data->wmi.info[type]" is
"const struct asus_wmi_sensor_info **", but the converted allocation type would be "const struct asus_wmi_sensor_info ***", as the size was taken from "*sensor_data->wmi.info", which is one level of indirection too many. Luckily both element types are pointers of the same size. Take the size from the element type of the assignment target.
Build tested ARCH=x86_64 allmodconfig with GCC 16.2.0:drivers/hwmon/asus_wmi_sensors.o
---
Cc: Ed Brindley <[email protected]>
Cc: Denis Pauk <[email protected]>
Cc: Guenter Roeck <[email protected]>
Cc: <[email protected]>
--- drivers/hwmon/asus_wmi_sensors.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/hwmon/asus_wmi_sensors.c +1 -1
@@ -573,7 +573,7 @@ static int asus_wmi_configure_sensor_setup(struct device *dev, sensor_data->wmi.info[type] =devm_kcalloc (dev, nr_count[type], -sizeof (*sensor_data->wmi.info), +sizeof (*sensor_data->wmi.info[type]),GFP_KERNEL );if (!sensor_data->wmi.info[type])return -ENOMEM ;
Signature · 1 line
2.34.1
[email protected]
AI reviewSashiko has reviewed this patch and found no issues. It looks great!
Quoted 15 lines
From: Kees Cook <[email protected]>
In preparation for making the
devm_kmallocfamily of allocators type aware, we need to make sure that the returned type from the allocation matches the type of the variable being assigned. (Before, the allocator would always return "void *", which can be implicitly cast to any pointer type.)The assigned type of "sensor_data->wmi.info[type]" is
"const structasus_wmi_sensor_info**", but the converted allocation type would be "const structasus_wmi_sensor_info***", as the size was taken from "*sensor_data->wmi.info", which is one level of indirection too many. Luckily both element types are pointers of the same size. Take the size from the element type of the assignment target.
Quoted 5 lines
Build tested ARCH=x86_64 allmodconfig with GCC 16.2.0:
drivers/hwmon/asus_wmi_sensors.oAssisted-by LLM coccinelleSigned-off-by Kees Cook <[email protected]>
Sashiko has reviewed this patch and found no issues. It looks great!
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=1
Quoted 15 lines · Kees Cook
From: Kees Cook <[email protected]>
In preparation for making the
devm_kmallocfamily of allocators type aware, we need to make sure that the returned type from the allocation matches the type of the variable being assigned. (Before, the allocator would always return "void *", which can be implicitly cast to any pointer type.)The assigned type of "sensor_data->wmi.info[type]" is
"const structasus_wmi_sensor_info**", but the converted allocation type would be "const structasus_wmi_sensor_info***", as the size was taken from "*sensor_data->wmi.info", which is one level of indirection too many. Luckily both element types are pointers of the same size. Take the size from the element type of the assignment target.
Quoted 5 lines
Build tested ARCH=x86_64 allmodconfig with GCC 16.2.0:
drivers/hwmon/asus_wmi_sensors.oAssisted-by LLM coccinelleSigned-off-by Kees Cook <[email protected]>
Applied.
Thanks,
Guenter