linux-kernel - Re: linux-next: build warning after merge of the pm tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 10 Apr 2018 09:05:39 +0200
From:   "Rafael J. Wysocki" <rjw@...ysocki.net>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build warning after merge of the pm tree

On Monday, April 9, 2018 3:24:38 AM CEST Stephen Rothwell wrote:
> 
> --Sig_/QL=OZEguM./+7xhHdQruHaV
> Content-Type: text/plain; charset=US-ASCII
> Content-Transfer-Encoding: quoted-printable
> 
> Hi Rafael,
> 
> After merging the pm tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
> 
> kernel/time/tick-sched.c: In function 'tick_nohz_idle_exit':
> kernel/time/tick-sched.c:1162:3: warning: 'now' may be used uninitialized i=
> n this function [-Wmaybe-uninitialized]
>    __tick_nohz_idle_restart_tick(ts, now);
>    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> kernel/time/tick-sched.c:1146:10: note: 'now' was declared here
>   ktime_t now;
>           ^~~
> 
> This appears to be a false positive.
> 
> And another in the x86_64 allmodconfig build:
> 
> kernel/time/tick-sched.c: In function 'tick_nohz_idle_exit':
> kernel/time/tick-sched.c:538:2: warning: 'now' may be used uninitialized in=
>  this function [-Wmaybe-uninitialized]
>   update_ts_time_stats(smp_processor_id(), ts, now, NULL);
>   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> kernel/time/tick-sched.c:1146:10: note: 'now' was declared here
>   ktime_t now;
>           ^~~
> 
> also looks like a false positive.

Yes, they are false positives AFAICS.

Cheers,
Rafael