linux-kernel - Question on compiler warning

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-next>] [day] [month] [year] [list]

Date:	Mon, 30 Dec 2013 19:24:51 -0600
From:	Larry Finger <Larry.Finger@...inger.net>
To:	linux-wireless <linux-wireless@...r.kernel.org>
CC:	Geert Uytterhoeven <geert@...ux-m68k.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Question on compiler warning

In his regular article entitled Build regressions/improvements in v3.13-rc6" 
(http://lkml.indiana.edu/hypermail/linux/kernel/1312.3/01550.html), Geert 
Uytterhoeven reports the following warning regression:

+ /scratch/kisskb/src/drivers/net/wireless/b43/phy_n.c: warning: 'val_addr' may 
be used uninitialized in this function [-Wuninitialized]: => 178:21

This warning does not show up on any of my compilers, and it should not as the 
initialization and usage of that variable both take place in conditional 
branches that are testing exactly the same pointer.

Despite the fact that the warning is bogus, should a patch be submitted to clear 
it? I lean toward "no" as an answer because that would mask the warning if there 
were some future change that screwed up the flow; however, I wanted to check 
with the community.

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