aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorJonathan Cameron <[email protected]>2020-07-22 16:50:42 +0100
committerJonathan Cameron <[email protected]>2020-08-22 11:38:54 +0100
commitf60e8bb84282b8e633956cfe74b4f0d64ca73cec (patch)
tree3b1855078a4b4b39b5e8053cb46d03e7cb2ef096 /tools/perf/scripts/python/export-to-postgresql.py
parent7e5ac1f2206eda414f90c698fe1820dee873394d (diff)
iio:proximity:mb1232: Fix timestamp alignment and prevent data leak.
One of a class of bugs pointed out by Lars in a recent review. iio_push_to_buffers_with_timestamp assumes the buffer used is aligned to the size of the timestamp (8 bytes). This is not guaranteed in this driver which uses a 16 byte s16 array on the stack As Lars also noted this anti pattern can involve a leak of data to userspace and that indeed can happen here. We close both issues by moving to a suitable structure in the iio_priv() data with alignment ensured by use of an explicit c structure. This data is allocated with kzalloc so no data can leak appart from previous readings. In this case the forced alignment of the ts is necessary to ensure correct padding on x86_32 where the s64 would only be 4 byte aligned. Fixes: 16b05261537e ("mb1232.c: add distance iio sensor with i2c") Reported-by: Lars-Peter Clausen <[email protected]> Cc: Andreas Klinger <[email protected]> Signed-off-by: Jonathan Cameron <[email protected]> Cc: <[email protected]> Reviewed-by: Andy Shevchenko <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions