linux-kernel - Re: [PATCH] scripts/kconfig/menu.c: warning: jump may be used uninitialized in this function

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 30 Oct 2013 11:03:23 +0530
From:	Madhavan Srinivasan <maddy@...ux.vnet.ibm.com>
To:	"Yann E. MORIN" <yann.morin.1998@...e.fr>,
	Christian Kujau <lists@...dbynature.de>
CC:	LKML <linux-kernel@...r.kernel.org>, mmarek@...e.cz,
	akpm@...ux-foundation.org
Subject: Re: [PATCH] scripts/kconfig/menu.c: warning: jump may be used uninitialized
 in this function

On Tuesday 29 October 2013 11:23 PM, Yann E. MORIN wrote:
> Christian, All,
> 
> On 2013-10-27 19:02 -0700, Christian Kujau spake thusly:
>> On Sun, 27 Oct 2013 at 18:28, Christian Kujau wrote:
>>> While doing "make oldconfig" on 3.12-rc7 with gcc-4.7.2 (Debian), the 
>>> following warning is printed:
>>>
>>>   HOSTCC  scripts/kconfig/zconf.tab.o
>>> In file included from scripts/kconfig/zconf.tab.c:2537:0:
>>> /usr/local/src/linux-git/scripts/kconfig/menu.c: In function ‘get_symbol_str’:
>>> /usr/local/src/linux-git/scripts/kconfig/menu.c:586:18: warning: ‘jump’ may be used uninitialized in this function [-Wmaybe-uninitialized]
>>> /usr/local/src/linux-git/scripts/kconfig/menu.c:547:19: note: ‘jump’ was declared here
>>
>> Grrr, only after I sent this message I found this was reported in 
>> September already by Madhavan Srinivasan:  https://lkml.org/lkml/2013/9/19/24
>>
>> Does anybody know the state of this fix?
> 
My bad, somehow this slipped from my todo list.

> The solution was to properly comment that this was a gcc issue, in that 
> this is a spurious error, does not appear in previous gcc versions, and
> has been fixed in later gcc versions.
> 
I also notice this with gcc 4.8.1 (20131002) build.

> Setting 'jump' to NULL may hide reall issues in case the code is changed
> in the future, so it is not appropriate a fix. Hence why the previously-
> submitted patches were not applied.
> 
> I'll take this on me to properly fix this. Thanks for the heads up.
> 
> Regards,
> Yann E. MORIN.
> 

--
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/