From: Blaisorblade <blaisorblade@yahoo.it>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [uml-devel] Re: Uml showstopper bugs for 2.6.14
Date: Wed, 28 Sep 2005 18:40:22 +0200 [thread overview]
Message-ID: <200509281840.23816.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20050928145250.GB11610@ccure.user-mode-linux.org>
On Wednesday 28 September 2005 16:52, Jeff Dike wrote:
> On Wed, Sep 28, 2005 at 02:15:18PM +0200, Blaisorblade wrote:
> > Do you know when this was introduced, and the last working UML version?
> It's always been broken, I think.
Ah, but you're talking of SKAS0.
In this case (which seems strange, given the number of people using x86_64 and
not complaining - or maybe it's just me who didn't say "enable frame
pointers" to any of the various bug reports), if the patch is not trivial
enough (it seems to be), make sure to at least force frame pointers.
Even if I think, if I understood the thing correctly, that this workaround is
not even guaranteed to work.
> It results from the stub having to
> sigreturn by hand because it has no access to the libc restorer, and thus
> needing to restore the stack pointer to where it was on entry. I did this
> by popping the requisite number of times.
> Bodo fixed this for i386,
By restoring in sp the address of first param (or something like that), right?
> and
> I need to do something similar for x86_64.
The bug killing almost everybody testing 2.6.12-bb? In this case, it's SKAS0
specific.
But especially, couldn't this be triggered by another GCC version, changing
the stack layout?
> Jeff
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Messenger: chiamate gratuite in tutto il mondo
http://it.messenger.yahoo.com
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2005-09-28 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 16:46 [uml-devel] Uml showstopper bugs for 2.6.14 Blaisorblade
2005-09-27 19:30 ` [uml-devel] " Jeff Dike
2005-09-28 12:15 ` Blaisorblade
2005-09-28 14:52 ` Jeff Dike
2005-09-28 16:40 ` Blaisorblade [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=200509281840.23816.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=akpm@osdl.org \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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