All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Bastian Blank <bastian@waldi.eu.org>, Ingo Molnar <mingo@elte.hu>,
	Ingo Molnar <mingo@redhat.com>,
	the arch/x86 maintainers <x86@kernel.org>,
	Stable Kernel <stable@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [Xen-devel] Re: [PATCH] xen: Disable stack protector for irq helper
Date: Mon, 12 Oct 2009 15:20:14 -0700	[thread overview]
Message-ID: <4AD3AB9E.5040202@goop.org> (raw)
In-Reply-To: <20091012211258.GA21213@wavehammer.waldi.eu.org>

On 10/12/09 14:12, Bastian Blank wrote:
> On Mon, Oct 12, 2009 at 10:52:08PM +0200, Ingo Molnar wrote:
>   
>> ping - any update about this fix? Since it fixes a real crash it would 
>> be nice to fix this for .32.
>>     
> It works nicely.
>
> But IMHO this whole infrastructure should go for now, at least until gcc
> is able to produce functions with this call convention on its own. Or it
> needs to be restricted to only assembler functions. The other users of
> this may only work because the stack protector is already disabled for
> arch/x86/xen/mmu.o.
>   

No, the infrastructure is fine and completely compliant with the ABI
(which doesn't change with stackprotector).  But there were a couple of
interrupt-related calls which didn't use the infrastructure properly,
and failed to preserve edx properly; we'd gotten away with it until now
because the called functions were very simple and didn't end up using
edx - until stackprotector.

The fix is to use the infrastructure consistently.

I'll put together a suitable patch.

    J

WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Bastian Blank <bastian@waldi.eu.org>, Ingo Molnar <mingo@elte.hu>,
	Ingo Molnar <mingo@redhat.com>,
	the arch/x86 maintainers <x86@kernel.org>,
	Stable Kernel <stable@kernel.org>,
	Linu
Subject: Re: Re: [PATCH] xen: Disable stack protector for irq helper
Date: Mon, 12 Oct 2009 15:20:14 -0700	[thread overview]
Message-ID: <4AD3AB9E.5040202@goop.org> (raw)
In-Reply-To: <20091012211258.GA21213@wavehammer.waldi.eu.org>

On 10/12/09 14:12, Bastian Blank wrote:
> On Mon, Oct 12, 2009 at 10:52:08PM +0200, Ingo Molnar wrote:
>   
>> ping - any update about this fix? Since it fixes a real crash it would 
>> be nice to fix this for .32.
>>     
> It works nicely.
>
> But IMHO this whole infrastructure should go for now, at least until gcc
> is able to produce functions with this call convention on its own. Or it
> needs to be restricted to only assembler functions. The other users of
> this may only work because the stack protector is already disabled for
> arch/x86/xen/mmu.o.
>   

No, the infrastructure is fine and completely compliant with the ABI
(which doesn't change with stackprotector).  But there were a couple of
interrupt-related calls which didn't use the infrastructure properly,
and failed to preserve edx properly; we'd gotten away with it until now
because the called functions were very simple and didn't end up using
edx - until stackprotector.

The fix is to use the infrastructure consistently.

I'll put together a suitable patch.

    J

  reply	other threads:[~2009-10-12 22:20 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-04 18:30 [PATCH] xen: Disable stack protector for irq helper Bastian Blank
2009-10-04 18:30 ` Bastian Blank
2009-10-04 23:06 ` Jeremy Fitzhardinge
2009-10-04 23:06   ` Jeremy Fitzhardinge
2009-10-05  1:35   ` Bastian Blank
2009-10-05  1:35     ` Bastian Blank
2009-10-05 17:21     ` Jeremy Fitzhardinge
2009-10-05 17:21       ` Jeremy Fitzhardinge
2009-10-05 22:43       ` [Xen-devel] " Bastian Blank
2009-10-05 22:43         ` Bastian Blank
2009-10-06  0:36         ` [Xen-devel] " Jeremy Fitzhardinge
2009-10-06  0:36           ` Jeremy Fitzhardinge
2009-10-06  3:30           ` [Xen-devel] " Bastian Blank
2009-10-06  3:30             ` Bastian Blank
2009-10-06 19:01             ` [Xen-devel] " Jeremy Fitzhardinge
2009-10-06 19:01               ` Jeremy Fitzhardinge
2009-10-07 16:35               ` [Xen-devel] " Bastian Blank
2009-10-07 16:35                 ` Bastian Blank
2009-10-08  0:33                 ` [Xen-devel] " Jeremy Fitzhardinge
2009-10-08  0:33                   ` Jeremy Fitzhardinge
2009-10-12 20:52                   ` [Xen-devel] " Ingo Molnar
2009-10-12 20:52                     ` Ingo Molnar
2009-10-12 21:12                     ` [Xen-devel] " Bastian Blank
2009-10-12 21:12                       ` Bastian Blank
2009-10-12 22:20                       ` Jeremy Fitzhardinge [this message]
2009-10-12 22:20                         ` Jeremy Fitzhardinge
2009-10-12 23:32                     ` [Xen-devel] " Jeremy Fitzhardinge
2009-10-12 23:32                       ` Jeremy Fitzhardinge
2009-10-13  7:25                       ` [tip:x86/urgent] x86/paravirt: Use normal calling sequences for irq enable/disable tip-bot for Jeremy Fitzhardinge
2009-10-13  7:25                         ` tip-bot for Jeremy Fitzhardinge
2009-10-05  1:52   ` [PATCH] xen: fbdev frontend needs xenbus frontend Bastian Blank

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=4AD3AB9E.5040202@goop.org \
    --to=jeremy@goop.org \
    --cc=bastian@waldi.eu.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=stable@kernel.org \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.