linux-kernel - Re: [PATCH v2] NVMe: silence GCC warning on 32 bit

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

Message-ID: <20140324133154.GD5777@linux.intel.com>
Date:	Mon, 24 Mar 2014 09:31:54 -0400
From:	Matthew Wilcox <willy@...ux.intel.com>
To:	Paul Bolle <pebolle@...cali.nl>
Cc:	Keith Busch <keith.busch@...el.com>,
	Geert Uytterhoeven <geert@...ux-m68k.org>,
	linux-kernel@...r.kernel.org, linux-nvme@...ts.infradead.org
Subject: Re: [PATCH v2] NVMe: silence GCC warning on 32 bit

On Mon, Mar 24, 2014 at 09:11:04AM -0400, Matthew Wilcox wrote:
> On Tue, Mar 04, 2014 at 10:36:07AM +0100, Paul Bolle wrote:
> > Also note that it's actually not clear to me why these warnings only
> > trigger on 32 bit. I guess there's some int/long conversion lurking
> > somewhere. I haven't found it. 
> 
> I bet you're using a different revision of the compiler on 32 and 64 bit.
> Different gcc revisions have different abilities to track initialisation.

I should try things myself before opening my big mouth.  Weird.  Using
gcc-4.8, I see the same thing.  Guess I should just apply the patch,
though it feels wrong to be initialising an entire struct just to silence
a bogus compiler warning :-(
--
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/