lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CALKJsrr2T1enr-uzB5s5ijN5=VOag4sP32vob0QCv=a-k2T4pg@mail.gmail.com>
Date: Mon, 17 Mar 2025 10:02:43 +0100
From: Silvano Seva <s.seva@...gma.it>
To: Jonathan Cameron <jic23@...nel.org>
Cc: a.greco@...gma.it, Lorenzo Bianconi <lorenzo@...nel.org>, 
	Lars-Peter Clausen <lars@...afoo.de>, linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/2] iio: imu: st_lsm6dsx: fix possible lockup in st_lsm6dsx_read_fifo

On Sat, Mar 15, 2025 at 7:36 PM Jonathan Cameron <jic23@...nel.org> wrote:
>
> On Tue, 11 Mar 2025 09:49:47 +0100
> Silvano Seva <s.seva@...gma.it> wrote:
>
> > Prevent st_lsm6dsx_read_fifo from falling in an infinite loop in case
> > pattern_len is equal to zero and the device FIFO is not empty.
> >
> > Fixes: 290a6ce11d93 ("iio: imu: add support to lsm6dsx driver")
> > Signed-off-by: Silvano Seva <s.seva@...gma.it>
> I think you could validly have kept Lorenzo's ack given this was
> just breaking the patch into two parts. I put it back and applied
> these with them marked for stable to the fixes-togreg branch of iio.git
>
Yes, sorry. I mistakenly dropped the "acked-by" when splitting the patch.

Thank you,
Silvano.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ