mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Arjan van de Ven <arjan@infradead.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [GIT PULL] Fix Xen boot with CONFIG_CC_STACKPROTECTOR
Date: Fri, 21 Aug 2009 10:27:40 +0200	[thread overview]
Message-ID: <20090821082740.GC23993@elte.hu> (raw)
In-Reply-To: <4A8D78C1.5070708@goop.org>


* Jeremy Fitzhardinge <jeremy@goop.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

      reply	other threads:[~2009-08-21  8:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-20  0:29 Jeremy Fitzhardinge
2009-08-20 10:06 ` Ingo Molnar
2009-08-20 16:00   ` H. Peter Anvin
2009-08-20 16:24   ` Jeremy Fitzhardinge
2009-08-21  8:27     ` Ingo Molnar [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090821082740.GC23993@elte.hu \
    --to=mingo@elte.hu \
    --cc=arjan@infradead.org \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome