diff options
| author | Kees Cook <kees+treewide@kernel.org> | 2026-09-17 14:13:33 -0700 |
|---|---|---|
| committer | Guenter Roeck <linux@roeck-us.net> | 2026-09-29 06:57:31 -0700 |
| commit | 0a79032ff9b3d05d341f19853aa7dab0949d5f41 (patch) | |
| tree | d3a6699a7622429abe97823f8886ec180aec94c7 /tools/lib/python | |
| parent | 8eb79f25c686fea4c904b3aaafa3583b9e12ef64 (diff) | |
| download | linux-next-0a79032ff9b3d05d341f19853aa7dab0949d5f41.tar.gz linux-next-0a79032ff9b3d05d341f19853aa7dab0949d5f41.zip | |
hwmon: (asus_wmi_sensors) Fix info[] allocation type
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
Assisted-by: LLM coccinelle
Signed-off-by: Kees Cook <kees+treewide@kernel.org>
Link: https://patch.msgid.link/20260917211332.i.711-kees@kernel.org
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Diffstat (limited to 'tools/lib/python')
0 files changed, 0 insertions, 0 deletions
