public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: "Colin King (gmail)" <colin.i.king@gmail.com>,
	Roger Lu <roger.lu@mediatek.com>
Cc: AngeloGioacchino Del Regno 
	<angelogioacchino.delregno@collabora.com>,
	Kevin Hilman <khilman@baylibre.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: soc: mediatek: SVS: introduce MTK SVS engine
Date: Wed, 22 Jun 2022 15:37:38 +0200	[thread overview]
Message-ID: <e09a4f5e-8fbf-be3b-85af-a6dad347f67f@gmail.com> (raw)
In-Reply-To: <7f995d57-c40b-6c32-e776-677ae1496769@gmail.com>

Hi Colin,

On 22/06/2022 14:02, Colin King (gmail) wrote:
> Hi,
> 
> static analysis on linux-next with clang scan-build has detected a null pointer 
> dereference in the following commit:
> 
> commit 681a02e9500073cd8b9c25a04f06166254b5a879
> Author: Roger Lu <roger.lu@mediatek.com>
> Date:   Mon May 16 08:43:07 2022 +0800
> 
>      soc: mediatek: SVS: introduce MTK SVS engine
> 
> 
> The issue is as follows:
> 
> static irqreturn_t svs_isr(int irq, void *data)
> {
>          struct svs_platform *svsp = data;
>          struct svs_bank *svsb = NULL;
>          unsigned long flags;
>          u32 idx, int_sts, svs_en;
> 
>          for (idx = 0; idx < svsp->bank_max; idx++) {
>                  svsb = &svsp->banks[idx];
>                  WARN(!svsb, "%s: svsb(%s) is null", __func__, svsb->name);
>                  spin_lock_irqsave(&svs_lock, flags);
>                  svsp->pbank = svsb;
> 
> 
> If svsb is null, then the WARN message will dereference it when printing 
> svsb->name.  Also, subsequent dereferences to sbsv will cause a null pointer 
> dereference, for example the svsp->pbank assignment.
> 
> Colin

The banks and bank_max are defined on a per SoC basis in the platform data [1]. 
The case that svsb is null would hint to a incorrect platform data. So I think 
that there is no real issue we need to fix.

Regards,
Matthias


[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git/tree/drivers/soc/mediatek/mtk-svs.c?h=v5.19-next/soc#n2237

      reply	other threads:[~2022-06-22 13:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 12:02 soc: mediatek: SVS: introduce MTK SVS engine Colin King (gmail)
2022-06-22 13:37 ` Matthias Brugger [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=e09a4f5e-8fbf-be3b-85af-a6dad347f67f@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=colin.i.king@gmail.com \
    --cc=khilman@baylibre.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roger.lu@mediatek.com \
    /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