All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Bryan Donlan <bdonlan@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, xen-devel@lists.xensource.com
Subject: Re: Bug: ptrace issues under x86_64 Xen kernel 2.6.29
Date: Sat, 25 Apr 2009 16:19:05 -0700	[thread overview]
Message-ID: <49F39A69.3090906@goop.org> (raw)
In-Reply-To: <3e8340490904251510r5938b773r7b313555c91e214a@mail.gmail.com>

Bryan Donlan wrote:
> On Sun, Mar 29, 2009 at 11:01 PM, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>   
>> Bryan Donlan wrote:
>>     
>>> Using 2.6.29 or 2.6.28 as a 64-bit Xen domU, a number of ptrace()
>>> users seem to have issues with unexpected breakpoints. ltrace and gdb
>>> both seem to be affected, under both 64-bit and 32-bit userspace.
>>> 32-bit kernels do not seem to be affected. Typical symptoms look like:
>>>
>>>       
>> It looks like this is because the kernel sets up int3 (breakpoint) and debug
>> (watchpoints, etc) to be on a separate debug stack in the tss.  Xen doesn't
>> do this (and doesn't appear to have a mechanism to do so), so I guess the
>> on-stack format isn't what the kernel expects.  Does the patch below work?
>>     
>
> Hi,
>
> Sorry for the late reply; this message never made it to my inbox for
> some reason...
> I did try the patch, and saw similar results to Mark; ptrace works,
> but lots of warnings:
>   

Thanks.  Those warnings are harmless, but I have an updated version of 
the fix to suppress them in xen-tip/next.

    J

WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Bryan Donlan <bdonlan@gmail.com>
Cc: xen-devel@lists.xensource.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Bug: ptrace issues under x86_64 Xen kernel 2.6.29
Date: Sat, 25 Apr 2009 16:19:05 -0700	[thread overview]
Message-ID: <49F39A69.3090906@goop.org> (raw)
In-Reply-To: <3e8340490904251510r5938b773r7b313555c91e214a@mail.gmail.com>

Bryan Donlan wrote:
> On Sun, Mar 29, 2009 at 11:01 PM, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>   
>> Bryan Donlan wrote:
>>     
>>> Using 2.6.29 or 2.6.28 as a 64-bit Xen domU, a number of ptrace()
>>> users seem to have issues with unexpected breakpoints. ltrace and gdb
>>> both seem to be affected, under both 64-bit and 32-bit userspace.
>>> 32-bit kernels do not seem to be affected. Typical symptoms look like:
>>>
>>>       
>> It looks like this is because the kernel sets up int3 (breakpoint) and debug
>> (watchpoints, etc) to be on a separate debug stack in the tss.  Xen doesn't
>> do this (and doesn't appear to have a mechanism to do so), so I guess the
>> on-stack format isn't what the kernel expects.  Does the patch below work?
>>     
>
> Hi,
>
> Sorry for the late reply; this message never made it to my inbox for
> some reason...
> I did try the patch, and saw similar results to Mark; ptrace works,
> but lots of warnings:
>   

Thanks.  Those warnings are harmless, but I have an updated version of 
the fix to suppress them in xen-tip/next.

    J

  reply	other threads:[~2009-04-25 23:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26  6:41 Bug: ptrace issues under x86_64 Xen kernel 2.6.29 Bryan Donlan
2009-03-26  6:41 ` Bryan Donlan
2009-03-26 19:15 ` Jeremy Fitzhardinge
2009-03-26 19:15   ` Jeremy Fitzhardinge
2009-03-30  3:01 ` Jeremy Fitzhardinge
2009-03-30  3:01   ` Jeremy Fitzhardinge
2009-04-07  7:46   ` Mark Wielaard
2009-04-25 22:10   ` Bryan Donlan
2009-04-25 22:10     ` Bryan Donlan
2009-04-25 23:19     ` Jeremy Fitzhardinge [this message]
2009-04-25 23:19       ` Jeremy Fitzhardinge

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=49F39A69.3090906@goop.org \
    --to=jeremy@goop.org \
    --cc=bdonlan@gmail.com \
    --cc=linux-kernel@vger.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.