From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: "Jiapeng Chong" <jiapeng.chong@linux.alibaba.com>,
mpe@ellerman.id.au, "Cédric Le Goater" <clg@kaod.org>
Cc: linuxppc-dev@lists.ozlabs.org, paulus@samba.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/xive: Fix unsigned comparison with less than zero
Date: Tue, 15 Mar 2022 10:17:40 +0100 [thread overview]
Message-ID: <bfdaba1e-333e-669b-e5c0-8a3e891ade35@csgroup.eu> (raw)
In-Reply-To: <1620382851-67480-1-git-send-email-jiapeng.chong@linux.alibaba.com>
Le 07/05/2021 à 12:20, Jiapeng Chong a écrit :
> The return from the call to irq_domain_alloc_irqs() is int, it can be
> a negative error code, however this is being assigned to an unsigned
> int variable 'irq', this may lead to invalid if statement detection,
> so that kfree execution is invalid. So making 'irq' an int.
>
> Clean up the following coccicheck warning:
>
> ./arch/powerpc/sysdev/xive/common.c:1157:6-14: WARNING: Unsigned
> expression compared with zero: xid -> irq < 0.
>
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
This was fixed by
https://github.com/linuxppc/linux/commit/3f601608b71c3ca1e199898cd16f09d707fedb56
> ---
> arch/powerpc/sysdev/xive/common.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/sysdev/xive/common.c b/arch/powerpc/sysdev/xive/common.c
> index a830432..a5fd45a 100644
> --- a/arch/powerpc/sysdev/xive/common.c
> +++ b/arch/powerpc/sysdev/xive/common.c
> @@ -65,7 +65,7 @@
> #ifdef CONFIG_SMP
> /* The IPIs use the same logical irq number when on the same chip */
> static struct xive_ipi_desc {
> - unsigned int irq;
> + int irq;
> char name[16];
> } *xive_ipis;
>
prev parent reply other threads:[~2022-03-15 9:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 10:20 [PATCH] powerpc/xive: Fix unsigned comparison with less than zero Jiapeng Chong
2022-03-15 9:17 ` Christophe Leroy [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=bfdaba1e-333e-669b-e5c0-8a3e891ade35@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=clg@kaod.org \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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