linux-kernel - Re: [Xen-devel] Re: Allow compile with CONFIG_DEBUG_INFO=y, X86

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]

Date:	Fri, 08 Aug 2008 08:21:41 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Adrian Bunk <bunk@...nel.org>
CC:	Mark McLoughlin <markmc@...hat.com>, xen-devel@...ts.xensource.com,
	Eduardo Habkost <ehabkost@...hat.com>,
	Stephen Tweedie <sct@...hat.com>, linux-kernel@...r.kernel.org,
	Simon Horman <horms@...ge.net.au>,
	"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	Dhaval Giani <dhaval@...ux.vnet.ibm.com>
Subject: Re: [Xen-devel] Re: Allow compile with CONFIG_DEBUG_INFO=y,	X86_PAE
 not set on gcc 3.4.5

Adrian Bunk wrote:
> CONFIG_DEBUG_INFO=y is why I never hit it before.
>
> It does not seem to be just one dodgy Redhat compiler (as I assumed in 
> the Bugzilla entry) but the whole 3.4 series of gcc which makes our 
> resolution of saying that this specific compiler is broken invalid.
>
> Considering that we officially support all compilers >= 3.2 this is just 
> one more case where we have to add to the kernel a workaround for a 
> broken compiler.
>   

Yes.  I'm happy to write off a specific rpm package, but a whole series 
is a different matter.

Adding

	if (PREALLOCATED_PMDS == 0)
		return;

in the appropriate places with a small comment seems like the right answer.

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