From: Daniel Jacobowitz <dan@debian.org>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Fabiano Ramos <ramos_fabiano@yahoo.com.br>,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
Andi Kleen <ak@muc.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ptrace in 2.6.5
Date: Tue, 11 May 2004 10:07:22 -0400 [thread overview]
Message-ID: <20040511140722.GA13568@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0405102340260.1156@bigblue.dev.mdolabs.com>
On Mon, May 10, 2004 at 11:41:53PM -0700, Davide Libenzi wrote:
> On Mon, 10 May 2004, Davide Libenzi wrote:
>
> > On Mon, 10 May 2004, Davide Libenzi wrote:
> >
> > > On the kernel side, this would be pretty much solved by issuing a ptrace
> > > op, with a modified EIP (+2) on return from a syscall (if in single-step
> > > mode).
> >
> > Actaully, the EIP should not be changed (since it already points to the
> > intruction following INT 0x80) and I believe it is sufficent to replace
> > the test for _TIF_SYSCALL_TRACE with (_TIF_SYSCALL_TRACE | TIF_SINGLESTEP)
> > in the system call return path. This should generate a ptrace trap with
> > EIP pointing to the next instruction following INT 0x80.
>
> The patch below (for i386) should work.
Yeah, that's what I was suggesting. I think the patch is right.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-05-11 14:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1UlcA-6lq-9@gated-at.bofh.it>
2004-05-10 18:49 ` ptrace in 2.6.5 Andi Kleen
2004-05-10 19:37 ` Davide Libenzi
2004-05-10 20:24 ` Fabiano Ramos
2004-05-10 21:49 ` OGAWA Hirofumi
2004-05-10 22:47 ` OGAWA Hirofumi
2004-05-10 22:58 ` Daniel Jacobowitz
2004-05-10 23:12 ` Davide Libenzi
2004-05-11 0:40 ` Fabiano Ramos
2004-05-11 6:14 ` Davide Libenzi
2004-05-11 6:27 ` Davide Libenzi
2004-05-11 6:41 ` Davide Libenzi
2004-05-11 14:07 ` Daniel Jacobowitz [this message]
2004-05-10 15:46 Fabiano Ramos
2004-05-10 16:10 ` Daniel Jacobowitz
2004-05-10 16:22 ` Fabiano Ramos
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=20040511140722.GA13568@nevyn.them.org \
--to=dan@debian.org \
--cc=ak@muc.de \
--cc=davidel@xmailserver.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=ramos_fabiano@yahoo.com.br \
/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.