[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YKNfgRWM9MK1MY9O@atomide.com>
Date: Tue, 18 May 2021 09:32:33 +0300
From: Tony Lindgren <tony@...mide.com>
To: Maciej Falkowski <maciej.falkowski9@...il.com>
Cc: khilman@...nel.org, aaro.koskinen@....fi, linux@...linux.org.uk,
linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, clang-built-linux@...glegroups.com
Subject: Re: [PATCH] ARM: OMAP: Fix use of possibly uninitialized irq variable
* Maciej Falkowski <maciej.falkowski9@...il.com> [210401 19:13]:
> The current control flow of IRQ number assignment to `irq` variable
> allows a request of IRQ of unspecified value,
> generating a warning under Clang compilation with omap1_defconfig on linux-next:
>
> arch/arm/mach-omap1/pm.c:656:11: warning: variable 'irq' is used uninitialized whenever
> 'if' condition is false [-Wsometimes-uninitialized]
> else if (cpu_is_omap16xx())
> ^~~~~~~~~~~~~~~~~
> ./arch/arm/mach-omap1/include/mach/soc.h:123:30: note: expanded from macro 'cpu_is_omap16xx'
> ^~~~~~~~~~~~~
> arch/arm/mach-omap1/pm.c:658:18: note: uninitialized use occurs here
> if (request_irq(irq, omap_wakeup_interrupt, 0, "peripheral wakeup",
> ^~~
> arch/arm/mach-omap1/pm.c:656:7: note: remove the 'if' if its condition is always true
> else if (cpu_is_omap16xx())
> ^~~~~~~~~~~~~~~~~~~~~~
> arch/arm/mach-omap1/pm.c:611:9: note: initialize the variable 'irq' to silence this warning
> int irq;
> ^
> = 0
Thanks applying into fixes.
Tony
Powered by blists - more mailing lists