linux-kernel - Re: posix_cpu_timer: initialize "now" variable

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:	Thu, 4 Apr 2013 15:50:23 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: posix_cpu_timer: initialize "now" variable

2013/4/4 Arnd Bergmann <arnd@...db.de>:
> Patch 6d0e025 "posix_cpu_timer: consolidate expiry time type" in linux-next
> introduces a new compiler warning:
>
> kernel/posix-cpu-timers.c: In function 'posix_cpu_timer_schedule':
> kernel/posix-cpu-timers.c:1127:19: warning: 'now' may be used uninitialized in this function [-Wmaybe-uninitialized]
>     clear_dead_task(timer, now);
>
> As far as I can tell, that warning is about an actual bug an not
> a false positive, as that variable is clearly never initialized
> when it gets used in line 1127.
>
> Here is a patch that makes the warning go away for me, no idea if this is
> the right solution or not.
>
> Signed-off-by: Arnd Bergmann <arnd@...db.de>

I posted a fix two days ago: https://lkml.org/lkml/2013/3/30/63

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/