From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
the arch/x86 maintainers <x86@kernel.org>,
Bastian Blank <bastian@waldi.eu.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>, Stable Kernel <stable@kernel.org>
Subject: Re: Re: [PATCH] xen: Disable stack protector for irq helper
Date: Mon, 12 Oct 2009 22:52:08 +0200 [thread overview]
Message-ID: <20091012205208.GE17163@elte.hu> (raw)
In-Reply-To: <4ACD3346.3010307@goop.org>
* Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> On 10/07/09 09:35, Bastian Blank wrote:
> > On Tue, Oct 06, 2009 at 12:01:12PM -0700, Jeremy Fitzhardinge wrote:
> >
> >> On 10/05/09 20:30, Bastian Blank wrote:
> >>
> >>> The original version saves ecx, but not edx. Both are official
> >>> caller-saved registers.
> >>>
> >> Hm. It doesn't save edx because that can be half of a 64-bit return
> >> value, and in general both eax and edx are marked clobbered.
> >>
> > Then it will be also wrong for functions returning void. They may
> > clobber eax but never set it to something correct.
> >
>
> The asm is marked as clobbering eax/edx, so the compiler knows it can't
> rely on them being preserved. void functions are not expected to
> preserve them either, so it all works out (or if they are, the compiler
> will do the right thing).
>
> Or did you have something else in mind?
>
>
> >> Except one
> >> place; does the patch below help?
> >>
> > Don't you need to remove the complete wrapper setup to get a correct
> > result? (And type safety.)
> >
>
> Which wrapper? Do you mean the callee-save function stuff? Or
> something else?
>
> It compiles cleanly for me and appears to work. Does it solve the
> problem for you?
>
> >>> Well, my call stack say something different. It crashs during early
> >>> startup without a console. The modifications to the function pointers is
> >>> done much later.
> >>>
> >> You're right. But you're holding out on me; can I see your backtrace?
> >>
> > Well, I'm traveling and it needs some time to recreate a broken kernel.
> >
> >
> >> And the disassembly of the troublesome code (both the Xen function and
> >> the calling function)?
> >>
> > That is easy.
> >
>
> OK, I see, thanks.
ping - any update about this fix? Since it fixes a real crash it would
be nice to fix this for .32.
Ingo
next prev parent reply other threads:[~2009-10-12 20:52 UTC|newest]
Thread overview: 16+ 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 23:06 ` Jeremy Fitzhardinge
2009-10-05 1:35 ` Bastian Blank
2009-10-05 17:21 ` Jeremy Fitzhardinge
2009-10-05 22:43 ` Bastian Blank
2009-10-06 0:36 ` Jeremy Fitzhardinge
2009-10-06 3:30 ` Bastian Blank
2009-10-06 19:01 ` Jeremy Fitzhardinge
2009-10-07 16:35 ` Bastian Blank
2009-10-08 0:33 ` Jeremy Fitzhardinge
2009-10-12 20:52 ` Ingo Molnar [this message]
2009-10-12 21:12 ` Bastian Blank
2009-10-12 22:20 ` 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-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=20091012205208.GE17163@elte.hu \
--to=mingo@elte.hu \
--cc=bastian@waldi.eu.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).