From: Jonathan Cameron <jic23@kernel.org>
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: linux-iio@vger.kernel.org,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Lorenzo Bianconi <lorenzo.bianconi83@gmail.com>
Subject: Re: [PATCH 12/25] iio:imu:st_lsm6dsx Fix alignment and data leak issues
Date: Sun, 7 Jun 2020 16:07:40 +0100 [thread overview]
Message-ID: <20200607160740.25df8024@archlinux> (raw)
In-Reply-To: <20200526075838.GC339643@localhost.localdomain>
On Tue, 26 May 2020 09:58:38 +0200
Lorenzo Bianconi <lorenzo@kernel.org> wrote:
> > From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> >
> > 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 an array of smaller elements 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 set of suitable structures in the iio_priv() data.
> >
> > This data is allocated with kzalloc so no data can leak apart from
> > previous readings.
> >
> > There has been a lot of churn in this driver, so likely backports
> > may be needed for stable.
> >
> > Fixes: 290a6ce11d93 ("iio: imu: add support to lsm6dsx driver")
> > Reported-by: Lars-Peter Clausen <lars@metafoo.de>
> > Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > Cc: Lorenzo Bianconi <lorenzo.bianconi83@gmail.com>
> > ---
> > drivers/iio/imu/st_lsm6dsx/st_lsm6dsx.h | 5 ++++
> > .../iio/imu/st_lsm6dsx/st_lsm6dsx_buffer.c | 27 ++++++++++---------
> > 2 files changed, 20 insertions(+), 12 deletions(-)
> >
> > diff --git a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx.h b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx.h
> > index b56df409ed0f..5bc724eadc83 100644
> > --- a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx.h
> > +++ b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx.h
> > @@ -411,6 +411,11 @@ struct st_lsm6dsx_hw {
> > const struct st_lsm6dsx_settings *settings;
> >
> > struct iio_mount_matrix orientation;
> > + /* Ensure natural alignment of buffer elements */
> > + struct {
> > + __le16 channels[3];
> > + s64 ts;
> > + } gyro_scan, acc_scan, ext_scan;
> > };
> >
> > static __maybe_unused const struct iio_event_spec st_lsm6dsx_event = {
> > diff --git a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_buffer.c b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_buffer.c
> > index afd00daeefb2..9bcffbfac797 100644
> > --- a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_buffer.c
> > +++ b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_buffer.c
> > @@ -341,9 +341,6 @@ int st_lsm6dsx_read_fifo(struct st_lsm6dsx_hw *hw)
> > int err, sip, acc_sip, gyro_sip, ts_sip, ext_sip, read_len, offset;
> > u16 fifo_len, pattern_len = hw->sip * ST_LSM6DSX_SAMPLE_SIZE;
> > u16 fifo_diff_mask = hw->settings->fifo_ops.fifo_diff.mask;
> > - u8 gyro_buff[ST_LSM6DSX_IIO_BUFF_SIZE];
> > - u8 acc_buff[ST_LSM6DSX_IIO_BUFF_SIZE];
> > - u8 ext_buff[ST_LSM6DSX_IIO_BUFF_SIZE];
> > bool reset_ts = false;
> > __le16 fifo_status;
> > s64 ts = 0;
> > @@ -404,18 +401,21 @@ int st_lsm6dsx_read_fifo(struct st_lsm6dsx_hw *hw)
> >
> > while (acc_sip > 0 || gyro_sip > 0 || ext_sip > 0) {
> > if (gyro_sip > 0 && !(sip % gyro_sensor->decimator)) {
> > - memcpy(gyro_buff, &hw->buff[offset],
> > - ST_LSM6DSX_SAMPLE_SIZE);
> > + memcpy(hw->gyro_scan.channels,
> > + &hw->buff[offset],
> > + sizeof(hw->gyro_scan.channels));
> > offset += ST_LSM6DSX_SAMPLE_SIZE;
>
> what about doing?
>
> offset += sizeof(hw->gyro_scan.channels)
>
> it seems easier to follow, what do you think?
>
> > }
> > if (acc_sip > 0 && !(sip % acc_sensor->decimator)) {
> > - memcpy(acc_buff, &hw->buff[offset],
> > - ST_LSM6DSX_SAMPLE_SIZE);
> > + memcpy(hw->acc_scan.channels,
> > + &hw->buff[offset],
> > + sizeof(hw->acc_scan.channels));
> > offset += ST_LSM6DSX_SAMPLE_SIZE;
>
> same here
>
> > }
> > if (ext_sip > 0 && !(sip % ext_sensor->decimator)) {
> > - memcpy(ext_buff, &hw->buff[offset],
> > - ST_LSM6DSX_SAMPLE_SIZE);
> > + memcpy(hw->ext_scan.channels,
> > + &hw->buff[offset],
> > + sizeof(hw->ext_scan.channels));
> > offset += ST_LSM6DSX_SAMPLE_SIZE;
>
> same here
Agreed. I also missed the tagged path needs alignment. For that one I did it
directly on the stack. Please take a look at v2 and let me know if it looks
right to you.
Thanks,
Jonathan
>
> Regards,
> Lorenzo
>
> > }
> >
> > @@ -446,19 +446,22 @@ int st_lsm6dsx_read_fifo(struct st_lsm6dsx_hw *hw)
> > if (gyro_sip > 0 && !(sip % gyro_sensor->decimator)) {
> > iio_push_to_buffers_with_timestamp(
> > hw->iio_devs[ST_LSM6DSX_ID_GYRO],
> > - gyro_buff, gyro_sensor->ts_ref + ts);
> > + &hw->gyro_scan,
> > + gyro_sensor->ts_ref + ts);
> > gyro_sip--;
> > }
> > if (acc_sip > 0 && !(sip % acc_sensor->decimator)) {
> > iio_push_to_buffers_with_timestamp(
> > hw->iio_devs[ST_LSM6DSX_ID_ACC],
> > - acc_buff, acc_sensor->ts_ref + ts);
> > + &hw->acc_scan,
> > + acc_sensor->ts_ref + ts);
> > acc_sip--;
> > }
> > if (ext_sip > 0 && !(sip % ext_sensor->decimator)) {
> > iio_push_to_buffers_with_timestamp(
> > hw->iio_devs[ST_LSM6DSX_ID_EXT0],
> > - ext_buff, ext_sensor->ts_ref + ts);
> > + &hw->ext_scan,
> > + ext_sensor->ts_ref + ts);
> > ext_sip--;
> > }
> > sip++;
> > --
> > 2.26.2
> >
next prev parent reply other threads:[~2020-06-07 15:07 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 17:06 [PATCH 00/25] IIO: 2nd set of timestamp alignment fixes Jonathan Cameron
2020-05-25 17:06 ` [PATCH 01/25] iio:light:si1145: Fix timestamp alignment and prevent data leak Jonathan Cameron
2020-05-25 17:06 ` [PATCH 02/25] iio:light:max44000 " Jonathan Cameron
2020-05-25 17:06 ` [PATCH 03/25] iio:light:rpr0521 " Jonathan Cameron
2020-05-25 17:06 ` [PATCH 04/25] iio:light:st_uvis25 " Jonathan Cameron
2020-05-26 7:55 ` Lorenzo Bianconi
2020-05-26 16:53 ` Jonathan Cameron
2020-06-07 14:37 ` Jonathan Cameron
2020-05-25 17:06 ` [PATCH 05/25] iio:light:ltr501 Fix timestamp alignment issue Jonathan Cameron
2020-05-25 17:06 ` [PATCH 06/25] iio:magnetometer:ak8974: Fix alignment and data leak issues Jonathan Cameron
2020-05-26 9:24 ` Linus Walleij
2020-06-07 14:43 ` Jonathan Cameron
2020-05-25 17:06 ` [PATCH 07/25] iio:magnetometer:ak8975 " Jonathan Cameron
2020-05-26 9:24 ` Andy Shevchenko
2020-05-26 16:50 ` Jonathan Cameron
2020-05-25 17:06 ` [PATCH 08/25] iio:magnetometer:mag3110 " Jonathan Cameron
2020-05-25 17:06 ` [PATCH 09/25] iio:humidity:hdc100x " Jonathan Cameron
2020-05-26 19:31 ` Matt Ranostay
2020-06-07 14:51 ` Jonathan Cameron
2020-05-25 17:06 ` [PATCH 10/25] iio:humidity:hts221 " Jonathan Cameron
2020-05-26 7:52 ` Lorenzo Bianconi
2020-06-07 14:55 ` Jonathan Cameron
2020-05-25 17:06 ` [PATCH 11/25] iio:imu:bmi160 " Jonathan Cameron
2020-05-25 17:06 ` [PATCH 12/25] iio:imu:st_lsm6dsx " Jonathan Cameron
2020-05-26 7:58 ` Lorenzo Bianconi
2020-06-07 15:07 ` Jonathan Cameron [this message]
2020-05-25 17:06 ` [PATCH 13/25] iio:imu:inv_mpu6050 Fix dma and ts " Jonathan Cameron
2020-05-25 18:44 ` Jean-Baptiste Maneyrol
2020-05-26 16:59 ` Jonathan Cameron
2020-05-25 17:06 ` [PATCH 14/25] iio:pressure:ms5611 Fix buffer element alignment Jonathan Cameron
2020-05-25 17:06 ` [PATCH 15/25] iio:pressure:mpl3115 Force alignment of buffer Jonathan Cameron
2020-05-25 17:06 ` [PATCH 16/25] iio:adc:ti-adc081c Fix alignment and data leak issues Jonathan Cameron
2020-05-25 17:06 ` [PATCH 17/25] iio:adc:ti-adc084s021 " Jonathan Cameron
2020-05-25 17:06 ` [PATCH 18/25] iio:adc:ti-adc084s021 Tidy up endian types Jonathan Cameron
2020-05-25 17:06 ` [PATCH 19/25] iio:adc:ti-ads1015 Fix buffer element alignment Jonathan Cameron
2020-05-25 17:52 ` Andy Shevchenko
2020-05-26 8:11 ` Lars-Peter Clausen
2020-05-26 9:15 ` Andy Shevchenko
2020-05-26 16:43 ` Jonathan Cameron
2020-05-26 17:06 ` Andy Shevchenko
2020-05-26 19:17 ` Jonathan Cameron
2020-05-26 21:03 ` Andy Shevchenko
2020-05-27 11:41 ` Jonathan Cameron
2020-05-27 12:37 ` Andy Shevchenko
2020-05-27 14:06 ` Andy Shevchenko
2020-05-27 14:43 ` Jonathan Cameron
2020-05-25 17:06 ` [PATCH 20/25] iio:adc:ti-ads124s08 Fix alignment and data leak issues Jonathan Cameron
2020-05-25 17:06 ` [PATCH 21/25] iio:adc:ti-ads8688 Fix alignment and potential data leak issue Jonathan Cameron
2020-05-25 17:06 ` [PATCH 22/25] iio:adc:ti-adc0832 Fix alignment issue with timestamp Jonathan Cameron
2020-05-25 17:06 ` [PATCH 23/25] iio:adc:ti-adc12138 " Jonathan Cameron
2020-05-25 17:06 ` [PATCH 24/25] iio:adc:ina2xx Fix timestamp alignment issue Jonathan Cameron
2020-05-25 17:06 ` [PATCH 25/25] iio:adc:max1118 Fix alignment of timestamp and data leak issues Jonathan Cameron
2020-05-26 17:02 ` [PATCH 00/25] IIO: 2nd set of timestamp alignment fixes Jonathan Cameron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200607160740.25df8024@archlinux \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=lorenzo.bianconi83@gmail.com \
--cc=lorenzo@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).