From: Jonathan Cameron <jic23@kernel.org>
To: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
Cc: Lorenzo Bianconi <lorenzo@kernel.org>,
<linux-iio@vger.kernel.org>, Lars-Peter Clausen <lars@metafoo.de>,
Lorenzo Bianconi <lorenzo.bianconi83@gmail.com>
Subject: Re: [PATCH 04/25] iio:light:st_uvis25 Fix timestamp alignment and prevent data leak.
Date: Sun, 7 Jun 2020 15:37:37 +0100 [thread overview]
Message-ID: <20200607153737.499cfa8c@archlinux> (raw)
In-Reply-To: <20200526175326.00007712@Huawei.com>
On Tue, 26 May 2020 17:53:26 +0100
Jonathan Cameron <Jonathan.Cameron@Huawei.com> wrote:
> On Tue, 26 May 2020 09:55:05 +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 suitable structure in the iio_priv()
> > >
> > > This data is allocated with kzalloc so no data can leak apart
> > > from previous readings.
> > >
> > > Fixes: 3025c8688c1e ("iio: light: add support for UVIS25 sensor")
> > > Reported-by: Lars-Peter Clausen <lars@metafoo.de>
> > > Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > > Cc: Lorenzo Bianconi <lorenzo.bianconi83@gmail.com>
> >
> > Acked-by: Lorenzo Bianconi <lorenzo@kernel.org>
>
> Unfortunately this is wrong (as Andy Schevchenko pointed out in one
> of the other patches). On x86_32 s64 is only aligned to 4 bytes
> so the size of the structure will end up too small for the IIO alignment
> rules.
>
> There will be a v2 once we've figure out the best, consistent solution.
Given the change is fairly small I've kept acks etc from V1. Hopefully
no one minds that.
Jonathan
>
> Sorry about that!
>
> Jonathan
>
> >
> > > ---
> > > drivers/iio/light/st_uvis25.h | 5 +++++
> > > drivers/iio/light/st_uvis25_core.c | 6 +++---
> > > 2 files changed, 8 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/drivers/iio/light/st_uvis25.h b/drivers/iio/light/st_uvis25.h
> > > index 78bc56aad129..f7027e4c4493 100644
> > > --- a/drivers/iio/light/st_uvis25.h
> > > +++ b/drivers/iio/light/st_uvis25.h
> > > @@ -27,6 +27,11 @@ struct st_uvis25_hw {
> > > struct iio_trigger *trig;
> > > bool enabled;
> > > int irq;
> > > + /* Ensure timestamp is naturally aligned */
> > > + struct {
> > > + u8 chan;
> > > + s64 ts;
> > > + } scan;
> > > };
> > >
> > > extern const struct dev_pm_ops st_uvis25_pm_ops;
> > > diff --git a/drivers/iio/light/st_uvis25_core.c b/drivers/iio/light/st_uvis25_core.c
> > > index d262c254b895..fe1f2dc970c7 100644
> > > --- a/drivers/iio/light/st_uvis25_core.c
> > > +++ b/drivers/iio/light/st_uvis25_core.c
> > > @@ -234,17 +234,17 @@ static const struct iio_buffer_setup_ops st_uvis25_buffer_ops = {
> > >
> > > static irqreturn_t st_uvis25_buffer_handler_thread(int irq, void *p)
> > > {
> > > - u8 buffer[ALIGN(sizeof(u8), sizeof(s64)) + sizeof(s64)];
> > > struct iio_poll_func *pf = p;
> > > struct iio_dev *iio_dev = pf->indio_dev;
> > > struct st_uvis25_hw *hw = iio_priv(iio_dev);
> > > int err;
> > >
> > > - err = regmap_read(hw->regmap, ST_UVIS25_REG_OUT_ADDR, (int *)buffer);
> > > + err = regmap_read(hw->regmap, ST_UVIS25_REG_OUT_ADDR,
> > > + (unsigned int *)&hw->scan.chan);
> > > if (err < 0)
> > > goto out;
> > >
> > > - iio_push_to_buffers_with_timestamp(iio_dev, buffer,
> > > + iio_push_to_buffers_with_timestamp(iio_dev, &hw->scan,
> > > iio_get_time_ns(iio_dev));
> > >
> > > out:
> > > --
> > > 2.26.2
> > >
> >
>
>
next prev parent reply other threads:[~2020-06-07 14:37 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 [this message]
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
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=20200607153737.499cfa8c@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).