linux-kernel - Re: [patch] firmware: qemu_fw_cfg.c: potential unintialized 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]

Message-ID: <20160414200500.GI4247@mwanda>
Date:	Thu, 14 Apr 2016 23:05:00 +0300
From:	Dan Carpenter <dan.carpenter@...cle.com>
To:	"Gabriel L. Somlo" <somlo@....edu>
Cc:	"Michael S. Tsirkin" <mst@...hat.com>, qemu-devel@...gnu.org,
	linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [patch] firmware: qemu_fw_cfg.c: potential unintialized variable

Ah...  I see now.  You're right.  Thanks for the explanation.

On my config those functions are no-ops so the variable isn't
initialized.  If they were enabled then *probably* it wouldn't generate
a warning.

Probably just silencing the warning is the way to go though...  I bet
GCC optimizes it away.  Let me think about this some more...

regards,
dan carpenter