mirror of
https://github.com/torvalds/linux.git
synced 2024-11-26 06:02:05 +00:00
ea191d0fd3
When compiling with gcc 13 with -Warray-bounds enabled:
In file included from drivers/iio/proximity/irsd200.c:15:
In function ‘iio_push_to_buffers_with_timestamp’,
inlined from ‘irsd200_trigger_handler’ at drivers/iio/proximity/irsd200.c:770:2:
./include/linux/iio/buffer.h:42:46: error: array subscript ‘int64_t {aka long long int}[0]’
is partly outside array bounds of ‘s16[1]’ {aka ‘short int[1]’} [-Werror=array-bounds=]
42 | ((int64_t *)data)[ts_offset] = timestamp;
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~
drivers/iio/proximity/irsd200.c: In function ‘irsd200_trigger_handler’:
drivers/iio/proximity/irsd200.c:763:13: note: object ‘buf’ of size 2
763 | s16 buf = 0;
| ^~~
The problem seems to be that irsd200_trigger_handler() is taking a s16
variable as an int64_t buffer. As Jonathan suggested [1], fix it by
extending the buffer to a two-element array of s64.
Link: https://github.com/KSPP/linux/issues/331
Link: https://lore.kernel.org/lkml/20230809181329.46c00a5d@jic23-huawei/ [1]
Fixes:
|
||
---|---|---|
.. | ||
as3935.c | ||
cros_ec_mkbp_proximity.c | ||
irsd200.c | ||
isl29501.c | ||
Kconfig | ||
Makefile | ||
mb1232.c | ||
ping.c | ||
pulsedlight-lidar-lite-v2.c | ||
rfd77402.c | ||
srf04.c | ||
srf08.c | ||
sx9310.c | ||
sx9324.c | ||
sx9360.c | ||
sx9500.c | ||
sx_common.c | ||
sx_common.h | ||
vcnl3020.c | ||
vl53l0x-i2c.c |