From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: "Yakov Lerner" <iler.ml@gmail.com>
Cc: prasanna@in.ibm.com, anil.s.keshavamurthy@intel.com,
davem@davemloft.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Subject: kprobes-x86: correct post-eip value in post_hander()
Date: Mon, 17 Mar 2008 10:49:56 +0530 [thread overview]
Message-ID: <20080317051956.GB7229@in.ibm.com> (raw)
In-Reply-To: <E1Jao7N-0005OC-Fe@io.site5.com>
On Sun, Mar 16, 2008 at 03:21:21AM -0500, Yakov Lerner wrote:
>
> I was trying to get the address of instruction to be executed
> next after the kprobed instruction. But regs->eip in post_handler()
> contains value which is useless to the user. It's pre-corrected value.
> This value is difficult to use without access to resume_execution(), which
> is not exported anyway.
> I moved the invocation of post_handler() to *after* resume_execution().
> Now regs->eip contains meaningful value in post_handler().
>
> I do not think this change breaks any backward-compatibility.
> To make meaning of the old value, post_handler() would need access to
> resume_execution() which is not exported. I have difficulty to believe
> that previous, uncorrected, regs->eip can be meaningfully used in
> post_handler().
resume_execution() exists not just for the program counter fixups after
out-of-line singlestepping, but is also as an insurance to put the
program counter back to the correct address in case the user's
post_handler() mucks around with it. That isn't possible with this
change :-(
Ananth
next prev parent reply other threads:[~2008-03-17 5:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-16 8:21 Yakov Lerner
2008-03-17 5:19 ` Ananth N Mavinakayanahalli [this message]
2008-03-17 10:59 ` Yakov Lerner
2008-03-17 12:39 ` Ananth N Mavinakayanahalli
2008-03-17 22:17 ` Masami Hiramatsu
2008-03-18 4:26 ` Ananth N Mavinakayanahalli
2008-03-21 11:08 ` Ingo Molnar
2008-03-21 11:31 ` Ananth N Mavinakayanahalli
2008-03-21 14:32 ` Ingo Molnar
2008-03-21 14:51 ` Ananth N Mavinakayanahalli
2008-03-21 23:18 ` Masami Hiramatsu
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=20080317051956.GB7229@in.ibm.com \
--to=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=iler.ml@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prasanna@in.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome