summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/task-analyzer.py
diff options
context:
space:
mode:
authorJiale Yao <yaojiale02@163.com>2026-09-25 20:57:44 +0800
committerJonathan Cameron <jonathan.cameron@oss.qualcomm.com>2026-09-28 17:07:35 +0100
commit4ac257f2fd2a9cac00e748486fa003b4e1cc453e (patch)
treea41110ad42462ba255aa4178c1cae8c2ac2536eb /tools/perf/scripts/python/task-analyzer.py
parentd3410a48d5eb9dd8238099cb0ee368d12005a385 (diff)
downloadlinux-next-4ac257f2fd2a9cac00e748486fa003b4e1cc453e.tar.gz
linux-next-4ac257f2fd2a9cac00e748486fa003b4e1cc453e.zip
iio: adc: ti-adc128s052: validate SPI match data
SPI driver_override allows a device to bind to this driver without matching either the firmware tables or SPI device ID table. In that case, spi_get_device_match_data() returns NULL. adc128_probe() also obtains the IIO device name by dereferencing the result of spi_get_device_id(), which is NULL on the same override path. The probe can therefore crash before it reaches the match data access. Commit 572a00852635 ("iio: dac: ad5686: missing NULL check on match data") fixed the same driver_override issue in another SPI driver. Reject devices without match data and use the always available SPI modalias for the IIO device name. Fixes: d5f0da0c6972 ("iio: adc: ti-adc128s052: Switch to use spi_get_device_match_data()") Cc: stable@vger.kernel.org Signed-off-by: Jiale Yao <yaojiale02@163.com> Signed-off-by: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions