linux-kernel - Re: linux-next: kvm tree build 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-prev] [day] [month] [year] [list]

Message-Id: <20100121000128.cf11525c.sfr@canb.auug.org.au>
Date:	Thu, 21 Jan 2010 00:01:28 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Alexander Graf <agraf@...e.de>
Cc:	Avi Kivity <avi@...ranet.com>,
	Marcelo Tosatti <mtosatti@...hat.com>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	ppc-dev <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: linux-next: kvm tree build warning

Hi Alex,

On Wed, 20 Jan 2010 11:42:28 +0100 Alexander Graf <agraf@...e.de> wrote:
>
> This is odd. The same function saves and restores ext_bkp.vrsave under a common condition:
> 
> So there can't be a case where ext_bkp.vrsave is read, but not written to before, which is what this warning implies, right?

Right.

> Also, why doesn't gcc complain about vscr too then? They're both used in the very same if statement.

I have no idea how gcc makes these decisions. :-(

> Additionally, while compiling locally I looked for warnings and didn't spot any. So apparently our compiler versions / options don't match. Which version of gcc are you using? I assume a gcc bug.
> 
> $ gcc --version
> gcc (SUSE Linux) 4.3.2 [gcc-4_3-branch revision 141291]

I use a 4.4.0 cross compiler (I should update it).
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/

Content of type "application/pgp-signature" skipped