aboutsummaryrefslogtreecommitdiffstats
path: root/lib/test_fortify/write_overflow-strlcpy-src.c
diff options
context:
space:
mode:
authorLinus Walleij <[email protected]>2025-11-03 09:36:18 +0000
committerJonathan Cameron <[email protected]>2025-11-11 20:22:23 +0000
commit3aa385a9c75c09b59dcab2ff76423439d23673ab (patch)
tree0c852d8ba7d626e48276b417978edf7fcddc7e01 /lib/test_fortify/write_overflow-strlcpy-src.c
parentiio: st_lsm6dsx: Fixed calibrated timestamp calculation (diff)
downloadkernel-3aa385a9c75c09b59dcab2ff76423439d23673ab.tar.gz
kernel-3aa385a9c75c09b59dcab2ff76423439d23673ab.zip
iio: accel: bmc150: Fix irq assumption regression
The code in bmc150-accel-core.c unconditionally calls bmc150_accel_set_interrupt() in the iio_buffer_setup_ops, such as on the runtime PM resume path giving a kernel splat like this if the device has no interrupts: Unable to handle kernel NULL pointer dereference at virtual address 00000001 when read PC is at bmc150_accel_set_interrupt+0x98/0x194 LR is at __pm_runtime_resume+0x5c/0x64 (...) Call trace: bmc150_accel_set_interrupt from bmc150_accel_buffer_postenable+0x40/0x108 bmc150_accel_buffer_postenable from __iio_update_buffers+0xbe0/0xcbc __iio_update_buffers from enable_store+0x84/0xc8 enable_store from kernfs_fop_write_iter+0x154/0x1b4 This bug seems to have been in the driver since the beginning, but it only manifests recently, I do not know why. Store the IRQ number in the state struct, as this is a common pattern in other drivers, then use this to determine if we have IRQ support or not. Cc: [email protected] Signed-off-by: Linus Walleij <[email protected]> Reviewed-by: Andy Shevchenko <[email protected]> Reviewed-by: Nuno Sá <[email protected]> Signed-off-by: Jonathan Cameron <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strlcpy-src.c')
0 files changed, 0 insertions, 0 deletions