From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: linux-media@vger.kernel.org, Maxime Ripard <mripard@kernel.org>,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Chen-Yu Tsai <wens@csie.org>,
Samuel Holland <samuel@sholland.org>,
Nicolas Dufresne <nicolas.dufresne@collabora.com>
Cc: kernel@collabora.com,
Dmitry Osipenko <dmitry.osipenko@collabora.com>,
stable@vger.kernel.org, linux-staging@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH v1 3/3] media: cedrus: Fix endless loop in cedrus_h265_skip_bits()
Date: Thu, 25 Aug 2022 23:13:52 +0200 [thread overview]
Message-ID: <1733932.VLH7GnMWUR@kista> (raw)
In-Reply-To: <52bb86cf12450ce78d2f196a1b86b4137ec61a07.camel@collabora.com>
Dne petek, 19. avgust 2022 ob 17:39:25 CEST je Nicolas Dufresne napisal(a):
> Le vendredi 19 août 2022 à 06:16 +0200, Jernej Škrabec a écrit :
> > Dne četrtek, 18. avgust 2022 ob 22:33:08 CEST je Nicolas Dufresne
napisal(a):
> > > From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
> > >
> > > The busy status bit may never de-assert if number of programmed skip
> > > bits is incorrect, resulting in a kernel hang because the bit is polled
> > > endlessly in the code. Fix it by adding timeout for the bit-polling.
> > > This problem is reproducible by setting the data_bit_offset field of
> > > the HEVC slice params to a wrong value by userspace.
> > >
> > > Cc: stable@vger.kernel.org
> > > Reported-by: Nicolas Dufresne <nicolas.dufresne@collabora.com>
> > > Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
> > > Signed-off-by: Nicolas Dufresne <nicolas.dufresne@collabora.com>
> >
> > Fixes tag would be nice.
> >
> > > ---
> > >
> > > drivers/staging/media/sunxi/cedrus/cedrus_h265.c | 6 ++++--
> > > 1 file changed, 4 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/staging/media/sunxi/cedrus/cedrus_h265.c
> > > b/drivers/staging/media/sunxi/cedrus/cedrus_h265.c index
> > > f703c585d91c5..f0bc118021b0a 100644
> > > --- a/drivers/staging/media/sunxi/cedrus/cedrus_h265.c
> > > +++ b/drivers/staging/media/sunxi/cedrus/cedrus_h265.c
> > > @@ -227,6 +227,7 @@ static void cedrus_h265_pred_weight_write(struct
> > > cedrus_dev *dev, static void cedrus_h265_skip_bits(struct cedrus_dev
> > > *dev,
> > > int num) {
> > >
> > > int count = 0;
> > >
> > > + u32 reg;
> > >
> > > while (count < num) {
> > >
> > > int tmp = min(num - count, 32);
> > >
> > > @@ -234,8 +235,9 @@ static void cedrus_h265_skip_bits(struct cedrus_dev
> > > *dev, int num) cedrus_write(dev, VE_DEC_H265_TRIGGER,
> > >
> > > VE_DEC_H265_TRIGGER_FLUSH_BITS |
> > > VE_DEC_H265_TRIGGER_TYPE_N_BITS(tmp));
> > >
> > > - while (cedrus_read(dev, VE_DEC_H265_STATUS) &
> > > VE_DEC_H265_STATUS_VLD_BUSY) - udelay(1);
> > > +
> > > + if (cedrus_wait_for(dev, VE_DEC_H265_STATUS,
> > > VE_DEC_H265_STATUS_VLD_BUSY)) +
> >
> > dev_err_ratelimited(dev->dev, "timed out
> >
> > > waiting to skip bits\n");
> >
> > Reporting issue is nice, but better would be to propagate error, since
> > there is no way to properly decode this slice if above code block fails.
> This mimic what was already there, mind if we do that later ? The
> propagation is doing to be a lot more intrusive.
Since backporting fixes before 6.0 isn't priority, viability for backpporting
isn't that important. You would only need to return 0 or -ETIMEDOUT and check
for error in only one location. That doesn't sound very intrusive for me.
Best regards,
Jernej
>
> > Best regards,
> > Jernej
> >
> > > count += tmp;
> > >
> > > }
WARNING: multiple messages have this Message-ID (diff)
From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: linux-media@vger.kernel.org, Maxime Ripard <mripard@kernel.org>,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Chen-Yu Tsai <wens@csie.org>,
Samuel Holland <samuel@sholland.org>,
Nicolas Dufresne <nicolas.dufresne@collabora.com>
Cc: kernel@collabora.com,
Dmitry Osipenko <dmitry.osipenko@collabora.com>,
stable@vger.kernel.org, linux-staging@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH v1 3/3] media: cedrus: Fix endless loop in cedrus_h265_skip_bits()
Date: Thu, 25 Aug 2022 23:13:52 +0200 [thread overview]
Message-ID: <1733932.VLH7GnMWUR@kista> (raw)
In-Reply-To: <52bb86cf12450ce78d2f196a1b86b4137ec61a07.camel@collabora.com>
Dne petek, 19. avgust 2022 ob 17:39:25 CEST je Nicolas Dufresne napisal(a):
> Le vendredi 19 août 2022 à 06:16 +0200, Jernej Škrabec a écrit :
> > Dne četrtek, 18. avgust 2022 ob 22:33:08 CEST je Nicolas Dufresne
napisal(a):
> > > From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
> > >
> > > The busy status bit may never de-assert if number of programmed skip
> > > bits is incorrect, resulting in a kernel hang because the bit is polled
> > > endlessly in the code. Fix it by adding timeout for the bit-polling.
> > > This problem is reproducible by setting the data_bit_offset field of
> > > the HEVC slice params to a wrong value by userspace.
> > >
> > > Cc: stable@vger.kernel.org
> > > Reported-by: Nicolas Dufresne <nicolas.dufresne@collabora.com>
> > > Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
> > > Signed-off-by: Nicolas Dufresne <nicolas.dufresne@collabora.com>
> >
> > Fixes tag would be nice.
> >
> > > ---
> > >
> > > drivers/staging/media/sunxi/cedrus/cedrus_h265.c | 6 ++++--
> > > 1 file changed, 4 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/staging/media/sunxi/cedrus/cedrus_h265.c
> > > b/drivers/staging/media/sunxi/cedrus/cedrus_h265.c index
> > > f703c585d91c5..f0bc118021b0a 100644
> > > --- a/drivers/staging/media/sunxi/cedrus/cedrus_h265.c
> > > +++ b/drivers/staging/media/sunxi/cedrus/cedrus_h265.c
> > > @@ -227,6 +227,7 @@ static void cedrus_h265_pred_weight_write(struct
> > > cedrus_dev *dev, static void cedrus_h265_skip_bits(struct cedrus_dev
> > > *dev,
> > > int num) {
> > >
> > > int count = 0;
> > >
> > > + u32 reg;
> > >
> > > while (count < num) {
> > >
> > > int tmp = min(num - count, 32);
> > >
> > > @@ -234,8 +235,9 @@ static void cedrus_h265_skip_bits(struct cedrus_dev
> > > *dev, int num) cedrus_write(dev, VE_DEC_H265_TRIGGER,
> > >
> > > VE_DEC_H265_TRIGGER_FLUSH_BITS |
> > > VE_DEC_H265_TRIGGER_TYPE_N_BITS(tmp));
> > >
> > > - while (cedrus_read(dev, VE_DEC_H265_STATUS) &
> > > VE_DEC_H265_STATUS_VLD_BUSY) - udelay(1);
> > > +
> > > + if (cedrus_wait_for(dev, VE_DEC_H265_STATUS,
> > > VE_DEC_H265_STATUS_VLD_BUSY)) +
> >
> > dev_err_ratelimited(dev->dev, "timed out
> >
> > > waiting to skip bits\n");
> >
> > Reporting issue is nice, but better would be to propagate error, since
> > there is no way to properly decode this slice if above code block fails.
> This mimic what was already there, mind if we do that later ? The
> propagation is doing to be a lot more intrusive.
Since backporting fixes before 6.0 isn't priority, viability for backpporting
isn't that important. You would only need to return 0 or -ETIMEDOUT and check
for error in only one location. That doesn't sound very intrusive for me.
Best regards,
Jernej
>
> > Best regards,
> > Jernej
> >
> > > count += tmp;
> > >
> > > }
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-08-25 21:13 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 20:33 [PATCH v1 0/3] cedrus: Various bug fixes Nicolas Dufresne
2022-08-18 20:33 ` [PATCH v1 1/3] media: cedrus: Fix watchdog race condition Nicolas Dufresne
2022-08-18 20:33 ` Nicolas Dufresne
2022-08-22 8:04 ` Paul Kocialkowski
2022-08-22 8:04 ` Paul Kocialkowski
2022-08-25 21:02 ` Jernej Škrabec
2022-08-25 21:02 ` Jernej Škrabec
2022-08-18 20:33 ` [PATCH v1 2/3] media: cedrus: Set the platform driver data earlier Nicolas Dufresne
2022-08-18 20:33 ` Nicolas Dufresne
2022-08-19 4:17 ` Jernej Škrabec
2022-08-19 4:17 ` Jernej Škrabec
2022-08-19 15:37 ` Nicolas Dufresne
2022-08-19 15:37 ` Nicolas Dufresne
2022-08-20 8:25 ` Jernej Škrabec
2022-08-20 8:25 ` Jernej Škrabec
2022-08-21 20:40 ` Dmitry Osipenko
2022-08-21 20:40 ` Dmitry Osipenko
2022-08-25 21:04 ` Jernej Škrabec
2022-08-25 21:04 ` Jernej Škrabec
2022-08-23 3:57 ` Samuel Holland
2022-08-23 3:57 ` Samuel Holland
2022-08-23 12:22 ` Paul Kocialkowski
2022-08-23 12:22 ` Paul Kocialkowski
2022-08-18 20:33 ` [PATCH v1 3/3] media: cedrus: Fix endless loop in cedrus_h265_skip_bits() Nicolas Dufresne
2022-08-18 20:33 ` Nicolas Dufresne
2022-08-18 20:39 ` Dmitry Osipenko
2022-08-18 20:39 ` Dmitry Osipenko
2022-08-18 21:17 ` Nicolas Dufresne
2022-08-18 21:17 ` Nicolas Dufresne
2022-08-19 4:16 ` Jernej Škrabec
2022-08-19 4:16 ` Jernej Škrabec
2022-08-19 15:39 ` Nicolas Dufresne
2022-08-19 15:39 ` Nicolas Dufresne
2022-08-25 21:13 ` Jernej Škrabec [this message]
2022-08-25 21:13 ` Jernej Škrabec
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=1733932.VLH7GnMWUR@kista \
--to=jernej.skrabec@gmail.com \
--cc=dmitry.osipenko@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-sunxi@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=mripard@kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=paul.kocialkowski@bootlin.com \
--cc=samuel@sholland.org \
--cc=stable@vger.kernel.org \
--cc=wens@csie.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.