All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Bastian Blank <waldi@debian.org>,
	linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
	544145@bugs.debian.org, Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: 32bit binaries on x86_64/Xen segfaults in syscall-vdso
Date: Fri, 04 Sep 2009 09:56:54 -0700	[thread overview]
Message-ID: <4AA146D6.8030802@goop.org> (raw)
In-Reply-To: <20090904162003.GA6147@wavehammer.waldi.eu.org>

On 09/04/09 09:20, Bastian Blank wrote:
> On Fri, Sep 04, 2009 at 09:07:39AM -0700, Jeremy Fitzhardinge wrote:
>   
>> But for some reason that's triggering a failsafe callback, which invokes
>> a GP.
>>     
> Hmm, not in my tests. It always returned to userspace correctly and died
> some operations later, usually the "ret". This then produced either a
> segfault (unreadable address), sigill (if it managed to reach the ELF
> header of the ld.so) or a GPF.

Hm, I may have misdiagnosed it then.  Your symptoms are odd; either its
landing back in userspace in the right place but then stumbles on for a
while before crashing (wrong processor mode?) or the eip is wrong and
its just landing in the wrong place and crashing immediately. 

How non-deterministic is it?  Does it differ every time, or from boot to
boot, build to build?

    J


  reply	other threads:[~2009-09-04 16:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-30 18:16 32bit binaries on x86_64/Xen segfaults in syscall-vdso Bastian Blank
2009-09-03 20:51 ` Jeremy Fitzhardinge
2009-09-03 22:02   ` Bastian Blank
2009-09-03 22:06     ` Jeremy Fitzhardinge
2009-09-03 22:36       ` Bastian Blank
2009-09-04 16:07         ` Jeremy Fitzhardinge
2009-09-04 16:20           ` Bastian Blank
2009-09-04 16:56             ` Jeremy Fitzhardinge [this message]
2009-09-04 17:46           ` Bastian Blank
2009-09-04 18:19             ` 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=4AA146D6.8030802@goop.org \
    --to=jeremy@goop.org \
    --cc=544145@bugs.debian.org \
    --cc=keir.fraser@eu.citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=waldi@debian.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.