public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Yakov Lerner <iler.ml@gmail.com>,
	prasanna@in.ibm.com, ananth@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: Fri, 21 Mar 2008 19:18:35 -0400	[thread overview]
Message-ID: <47E4424B.4060802@redhat.com> (raw)
In-Reply-To: <20080321110804.GY20420@elte.hu>

Ingo Molnar wrote:
> * Yakov Lerner <iler.ml@gmail.com> 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().
> 
> thanks, i've added your patch to the .26 bucket of x86.git, but it would 
> be nice to get an Ack/Nack from a kprobes person as well.
> 
> 	Ingo

Ingo, I also tested this on x86-64/x86/ia64.

Acked-by: Masami Hiramatsu <mhiramat@redhat.com>

Thanks,

-- 
Masami Hiramatsu

Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division

e-mail: mhiramat@redhat.com


      parent reply	other threads:[~2008-03-21 23:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-16  8:21 [PATCH] Subject: kprobes-x86: correct post-eip value in post_hander() Yakov Lerner
2008-03-17  5:19 ` Ananth N Mavinakayanahalli
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 [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=47E4424B.4060802@redhat.com \
    --to=mhiramat@redhat.com \
    --cc=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=mingo@elte.hu \
    --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