From: Dan Carpenter <dan.carpenter@linaro.org>
To: Valentina Fernandez <valentina.fernandezalanis@microchip.com>
Cc: jassisinghbrar@gmail.com, conor.dooley@microchip.com,
linux-kernel@vger.kernel.org, lkp@intel.com
Subject: Re: [PATCH v1] mailbox: mchp-ipc-sbi: fix uninitialized symbol and other smatch warnings
Date: Thu, 18 Dec 2025 14:35:20 +0300 [thread overview]
Message-ID: <aUPm-NsUJXxV8FT0@stanley.mountain> (raw)
In-Reply-To: <aUPkF9XuB3sRy6JP@stanley.mountain>
On Thu, Dec 18, 2025 at 02:23:03PM +0300, Dan Carpenter wrote:
> On Thu, Dec 18, 2025 at 10:33:59AM +0000, Valentina Fernandez wrote:
> > Fix uninitialized symbol 'hartid' warning in mchp_ipc_cluster_aggr_isr()
> > by introducing a 'found' flag to track whether the IRQ matches any
> > online hart. If no match is found, return IRQ_NONE.
> >
> > Also fix other smatch warnings by removing dead code in
> > mchp_ipc_startup() and by returning -ENODEV in dev_err_probe() if the
> > Microchip SBI extension is not found.
> >
> > Fixes below smatch warnings:
> > drivers/mailbox/mailbox-mchp-ipc-sbi.c:187 mchp_ipc_cluster_aggr_isr() error: uninitialized symbol 'hartid'.
> > drivers/mailbox/mailbox-mchp-ipc-sbi.c:324 mchp_ipc_startup() warn: ignoring unreachable code.
> > drivers/mailbox/mailbox-mchp-ipc-sbi.c:422 mchp_ipc_probe() warn: passing zero to 'dev_err_probe'
> >
> > Reported-by: kernel test robot <lkp@intel.com>
> > Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
> > Closes: https://lore.kernel.org/r/202512171533.CDLdScMY-lkp@intel.com/
> > Signed-off-by: Valentina Fernandez <valentina.fernandezalanis@microchip.com>
> > ---
> > drivers/mailbox/mailbox-mchp-ipc-sbi.c | 21 +++++++++------------
> > 1 file changed, 9 insertions(+), 12 deletions(-)
> >
> > diff --git a/drivers/mailbox/mailbox-mchp-ipc-sbi.c b/drivers/mailbox/mailbox-mchp-ipc-sbi.c
> > index d444491a584e..b87bf2fb4b9b 100644
> > --- a/drivers/mailbox/mailbox-mchp-ipc-sbi.c
> > +++ b/drivers/mailbox/mailbox-mchp-ipc-sbi.c
> > @@ -174,17 +174,21 @@ static irqreturn_t mchp_ipc_cluster_aggr_isr(int irq, void *data)
> > struct mchp_ipc_msg ipc_msg;
> > struct mchp_ipc_status status_msg;
> > int ret;
> > - unsigned long hartid;
> > u32 i, chan_index, chan_id;
> > + bool found = false;
> >
> > /* Find out the hart that originated the irq */
> > for_each_online_cpu(i) {
> > - hartid = cpuid_to_hartid_map(i);
> > - if (irq == ipc->cluster_cfg[i].irq)
> > + if (irq == ipc->cluster_cfg[i].irq) {
> > + found = true;
> > break;
> > + }
> > }
> >
> > - status_msg.cluster = hartid;
> > + if (unlikely(!found))
> > + return IRQ_NONE;
>
> This one is a false positive because obviously there is going to be
> at least one online cpu. I would prefer to silence this in Smatch.
> Generally, you should ignore static checker false positives.
Well... I guess the bug is real, but the warning was bogus. It was
a broken clock warning which works by chance twice a day.
regards,
dan carpenter
next prev parent reply other threads:[~2025-12-18 11:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 10:33 [PATCH v1] mailbox: mchp-ipc-sbi: fix uninitialized symbol and other smatch warnings Valentina Fernandez
2025-12-18 11:23 ` Dan Carpenter
2025-12-18 11:35 ` Dan Carpenter [this message]
2026-01-18 20:53 ` Jassi Brar
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=aUPm-NsUJXxV8FT0@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=conor.dooley@microchip.com \
--cc=jassisinghbrar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=valentina.fernandezalanis@microchip.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