mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: "Kirill A. Shutemov" <kirill@shutemov.name>,
	linux-arm-kernel@lists.arm.linux.org.uk,
	Nicolas Pitre <nico@cam.org>,
	linux-kernel@vger.kernel.org, linux@arm.linux.org.uk
Subject: Re: ERESTART_RESTARTBLOCK and ptrace()
Date: Fri, 12 Jun 2009 14:10:20 +0300	[thread overview]
Message-ID: <cc557aab0906120410h71e3ab59neeaf85c3223fd7c6@mail.gmail.com> (raw)
In-Reply-To: <20090611142700.GA12259@caradoc.them.org>

On Thu, Jun 11, 2009 at 5:27 PM, Daniel Jacobowitz<dan@debian.org> wrote:
> On Wed, Jun 10, 2009 at 01:25:34PM +0300, Kirill A. Shutemov wrote:
>> I've got bug in handling ERESTART_RESTARTBLOCK. Kernel version is 2.6.28.
>>
>> Steps to reproduce:
>> 1. Attach using ptrace() to process while it's in a syscall which use
>> ERESTART_RESTARTBLOCK
>> on interrupt. The easiest way is to attach to process which is in nanosleep().
>> 2. Run a syscall in context of the process like it does gdb.
>> 3. Continue the process.
>>
>> Results:
>> Syscall(nanosleep) return error code 516(ERESTART_RESTARTBLOCK). It's
>> kernel's internal error
>> code and should never appear at userspace.
>>
>> It seems ARM-related since I can't reproduce it on x86.
>
> That's because GDB has code to do the right thing on x86.  Consider
> filing a GDB bug please.

http://sourceware.org/bugzilla/show_bug.cgi?id=10267

      reply	other threads:[~2009-06-12 11:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10 10:25 Kirill A. Shutemov
2009-06-11 14:27 ` Daniel Jacobowitz
2009-06-12 11:10   ` Kirill A. Shutemov [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=cc557aab0906120410h71e3ab59neeaf85c3223fd7c6@mail.gmail.com \
    --to=kirill@shutemov.name \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=nico@cam.org \
    /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

all inboxes | Powered by JetHome®