From: Silvano Seva <s.seva@4sigma.it>
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: a.greco@4sigma.it, Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
"open list:ST LSM6DSx IMU IIO DRIVER"
<linux-iio@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] iio: imu: st_lsm6dsx: fix possible lockup during FIFO read
Date: Mon, 10 Mar 2025 14:29:30 +0100 [thread overview]
Message-ID: <CALKJsrodHaDdra2ZMzHkHmcZy+KMwbaO5jTSkSOx5S27SByecQ@mail.gmail.com> (raw)
In-Reply-To: <Z8sFdGG4bDyALrsi@lore-desk>
On Fri, Mar 7, 2025 at 3:40 PM Lorenzo Bianconi <lorenzo@kernel.org> wrote:
>
> > On Thu, Mar 6, 2025 at 4:48 PM Lorenzo Bianconi <lorenzo@kernel.org> wrote:
> > >
> > > > Prevent st_lsm6dsx_read_fifo and st_lsm6dsx_read_tagged_fifo functions
> > > > from falling in an infinite loop in case pattern_len is equal to zero and
> > > > the device FIFO is not empty.
> > > >
> > > > Signed-off-by: Silvano Seva <s.seva@4sigma.it>
> > > > ---
> > > > drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_buffer.c | 8 ++++++++
> > > > 1 file changed, 8 insertions(+)
> > > >
> > > > diff --git a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_buffer.c b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_buffer.c
> > > > index 0a7cd8c1aa33..7f343614f8a5 100644
> > > > --- a/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_buffer.c
> > > > +++ b/drivers/iio/imu/st_lsm6dsx/st_lsm6dsx_buffer.c
> > > > @@ -395,12 +395,17 @@ int st_lsm6dsx_read_fifo(struct st_lsm6dsx_hw *hw)
> > > > fifo_len = (le16_to_cpu(fifo_status) & fifo_diff_mask) *
> > > > ST_LSM6DSX_CHAN_SIZE;
> > > > fifo_len = (fifo_len / pattern_len) * pattern_len;
> > > > + if (!fifo_len)
> > > > + return 0;
> > >
> > > I do not think this check is necessary since if fifo_len is 0 we will not run
> > > the for loop, right?
> >
> > This check is present in the st_lsm6dsx_read_tagged_fifo() function, i
> > added it here for consistency. I agree with you that is not strictly
> > necessary.
> >
> > >
> > > >
> > > > acc_sensor = iio_priv(hw->iio_devs[ST_LSM6DSX_ID_ACC]);
> > > > gyro_sensor = iio_priv(hw->iio_devs[ST_LSM6DSX_ID_GYRO]);
> > > > if (hw->iio_devs[ST_LSM6DSX_ID_EXT0])
> > > > ext_sensor = iio_priv(hw->iio_devs[ST_LSM6DSX_ID_EXT0]);
> > > >
> > > > + if (!pattern_len)
> > > > + pattern_len = ST_LSM6DSX_SAMPLE_SIZE;
> > >
> > > same here, I do not think pattern_len can be 0 since hw->sip must be greater
> > > than 0 in order to enable the FIFO. Moreover, this check should be some lines
> > > above since we have already divided fifo_len by pattern_len here.
> > >
> >
> > There is a situation causing the subsequent for loop to never
> > terminate, hanging the kernel boot process: given a system which
> > doesn't have an hardware reset line allowing the kernel to
> > re-initialize the IMU hardware, in case of an hot reboot the driver
> > probe() function attempts to flush the FIFO, which may contain some
> > data, while the hw->sip is zero.
> > The complete execution path is the following:
> > - call of st_lsm6dsx_probe();
> > - allocation of the st_lsm6dsx_hw structure via the devm_kzalloc,
> > zero-initializing the sip field;
> > - call of st_lsm6dsx_init_device();
> > - call of st_lsm6dsx_reset_device();
> > - call of st_lsm6dsx_flush_fifo();
> > - call of st_lsm6dsx_read_fifo/st_lsm6dsx_read_tagged_fifo via the
> > fifo_ops function pointer.
>
> ack, I can see the issue now, thx for pointing this out. I should we should set
> pattern_len to ST_LSM6DSX_SAMPLE_SIZE or ST_LSM6DSX_TAGGED_SAMPLE_SIZE if it is
> 0. Can you please move the check before updating fifo_len in
> st_lsm6dsx_read_fifo()?
>
> Regards,
> Lorenzo
>
Changes done, I sent the updated patch in a separate reply email: I
hope that doing so didn't cause any trouble.
Thank you,
Silvano.
next prev parent reply other threads:[~2025-03-10 13:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 13:21 [PATCH] iio: imu: st_lsm6dsx: fix possible lockup during FIFO read Silvano Seva
2025-03-06 15:48 ` Lorenzo Bianconi
2025-03-07 9:20 ` Silvano Seva
2025-03-07 14:40 ` Lorenzo Bianconi
2025-03-10 13:22 ` Silvano Seva
2025-03-10 13:29 ` Silvano Seva [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-10 13:36 Lorenzo Bianconi
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=CALKJsrodHaDdra2ZMzHkHmcZy+KMwbaO5jTSkSOx5S27SByecQ@mail.gmail.com \
--to=s.seva@4sigma.it \
--cc=a.greco@4sigma.it \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).