mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Lucas Stach <l.stach@pengutronix.de>,
	Tobias Jordan <Tobias.Jordan@elektrobit.com>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [v3] gpu: ipu-v3: prg: avoid possible array underflow
Date: Thu, 15 Mar 2018 17:53:09 +0100	[thread overview]
Message-ID: <1521132789.4624.4.camel@pengutronix.de> (raw)
In-Reply-To: <20180315162011.807909-1-arnd@arndb.de>

Hi Arnd,

On Thu, 2018-03-15 at 17:19 +0100, Arnd Bergmann wrote:
> gcc-8 reports that we access an array with a negative index
> in an error case:
> 
> drivers/gpu/ipu-v3/ipu-prg.c: In function 'ipu_prg_channel_disable':
> drivers/gpu/ipu-v3/ipu-prg.c:252:43: error: array subscript -22 is below array bounds of 'struct ipu_prg_channel[3]' [-Werror=array-bounds]
> 
> This moves the range check in front of the first time that
> variable gets used.
> 
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>

thank you, I've replaced v2 with this version in imx-drm/fixes.

regards
Philipp

> ----
> v1: Originally sent on Dec 4, 2017.
> v2: Sent again on Jan 16, after no reply, Phillipp said it was merged
> v3: Ran into a related problem with CONFIG_UBSAN, sent again fixing both
> ---
>  drivers/gpu/ipu-v3/ipu-prg.c | 12 +++++++++---
>  1 file changed, 9 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/gpu/ipu-v3/ipu-prg.c b/drivers/gpu/ipu-v3/ipu-prg.c
> index 97b99500153d..83f9dd934a5d 100644
> --- a/drivers/gpu/ipu-v3/ipu-prg.c
> +++ b/drivers/gpu/ipu-v3/ipu-prg.c
> @@ -250,10 +250,14 @@ void ipu_prg_channel_disable(struct ipuv3_channel *ipu_chan)
>  {
>  	int prg_chan = ipu_prg_ipu_to_prg_chan(ipu_chan->num);
>  	struct ipu_prg *prg = ipu_chan->ipu->prg_priv;
> -	struct ipu_prg_channel *chan = &prg->chan[prg_chan];
> +	struct ipu_prg_channel *chan;
>  	u32 val;
>  
> -	if (!chan->enabled || prg_chan < 0)
> +	if (prg_chan < 0)
> +		return;
> +
> +	chan = &prg->chan[prg_chan];
> +	if (!chan->enabled)
>  		return;
>  
>  	pm_runtime_get_sync(prg->dev);
> @@ -280,13 +284,15 @@ int ipu_prg_channel_configure(struct ipuv3_channel *ipu_chan,
>  {
>  	int prg_chan = ipu_prg_ipu_to_prg_chan(ipu_chan->num);
>  	struct ipu_prg *prg = ipu_chan->ipu->prg_priv;
> -	struct ipu_prg_channel *chan = &prg->chan[prg_chan];
> +	struct ipu_prg_channel *chan;
>  	u32 val;
>  	int ret;
>  
>  	if (prg_chan < 0)
>  		return prg_chan;
>  
> +	chan = &prg->chan[prg_chan];
> +
>  	if (chan->enabled) {
>  		ipu_pre_update(prg->pres[chan->used_pre], *eba);
>  		return 0;

      reply	other threads:[~2018-03-15 16:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 16:19 Arnd Bergmann
2018-03-15 16:53 ` Philipp Zabel [this message]

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=1521132789.4624.4.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=Tobias.Jordan@elektrobit.com \
    --cc=arnd@arndb.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=l.stach@pengutronix.de \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®