linux-kernel - Re: [GIT PULL] Fix Xen boot with CONFIG_CC

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: <20090821082740.GC23993@elte.hu>
Date:	Fri, 21 Aug 2009 10:27:40 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Arjan van de Ven <arjan@...radead.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	the arch/x86 maintainers <x86@...nel.org>
Subject: Re: [GIT PULL] Fix Xen boot with CONFIG_CC_STACKPROTECTOR


* Jeremy Fitzhardinge <jeremy@...p.org> wrote:

> On 08/20/09 03:06, Ingo Molnar wrote:
> >> I only need to disable stackprotector for a
> >> handful of functions, but unfortunately it looks like it can only be
> >> disabled on a per-file basis.
> > Pulled into tip:x86/urgent, thanks a lot Jeremy!
> >
> > Btw., is there any way to turn off stackprotector on a 
> > per function basis, a GCC attribute perhaps? That would 
> > be preferable to turning it off for all of common.o.
> 
> Yeah, its awkward.  But it looks like this patch is not 
> sufficient, so drop it for now.  I'll send a replacement shortly 
> (though it doesn't hurt to keep it; I can just generate a delta if 
> that's better).

I already pulled it as the fixes looked right so please send a delta 
based on top of tip:x86/urgent.

Thanks,

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