linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Eugene Shatokhin <eugene.shatokhin@rosalab.ru>,
	Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] kprobes/x86: Return correct length in __copy_instruction()
Date: Tue, 10 Mar 2015 11:59:32 +0900	[thread overview]
Message-ID: <54FE5E14.8090303@hitachi.com> (raw)
In-Reply-To: <1425899954-24380-1-git-send-email-eugene.shatokhin@rosalab.ru>

(2015/03/09 20:19), Eugene Shatokhin wrote:
> On x86-64, __copy_instruction() always returns 0 (error) if the
> instruction uses %rip-relative addressing. This is because
> kernel_insn_init() is called the second time for 'insn' instance
> in such cases and sets all its fields to 0.
> 
> Because of this, trying to place a Kprobe on such instruction will
> fail, register_kprobe() will return -EINVAL.

Oops, good catch!

Acked-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>

Thank you!

> 
> This patch fixes the problem.
> 
> Signed-off-by: Eugene Shatokhin <eugene.shatokhin@rosalab.ru>
> ---
>  arch/x86/kernel/kprobes/core.c | 9 ++++++---
>  1 file changed, 6 insertions(+), 3 deletions(-)
> 
> diff --git a/arch/x86/kernel/kprobes/core.c b/arch/x86/kernel/kprobes/core.c
> index 4e3d5a9..03189d8 100644
> --- a/arch/x86/kernel/kprobes/core.c
> +++ b/arch/x86/kernel/kprobes/core.c
> @@ -354,6 +354,7 @@ int __copy_instruction(u8 *dest, u8 *src)
>  {
>  	struct insn insn;
>  	kprobe_opcode_t buf[MAX_INSN_SIZE];
> +	int length;
>  	unsigned long recovered_insn =
>  		recover_probed_instruction(buf, (unsigned long)src);
>  
> @@ -361,16 +362,18 @@ int __copy_instruction(u8 *dest, u8 *src)
>  		return 0;
>  	kernel_insn_init(&insn, (void *)recovered_insn, MAX_INSN_SIZE);
>  	insn_get_length(&insn);
> +	length = insn.length;
> +
>  	/* Another subsystem puts a breakpoint, failed to recover */
>  	if (insn.opcode.bytes[0] == BREAKPOINT_INSTRUCTION)
>  		return 0;
> -	memcpy(dest, insn.kaddr, insn.length);
> +	memcpy(dest, insn.kaddr, length);
>  
>  #ifdef CONFIG_X86_64
>  	if (insn_rip_relative(&insn)) {
>  		s64 newdisp;
>  		u8 *disp;
> -		kernel_insn_init(&insn, dest, insn.length);
> +		kernel_insn_init(&insn, dest, length);
>  		insn_get_displacement(&insn);
>  		/*
>  		 * The copied instruction uses the %rip-relative addressing
> @@ -394,7 +397,7 @@ int __copy_instruction(u8 *dest, u8 *src)
>  		*(s32 *) disp = (s32) newdisp;
>  	}
>  #endif
> -	return insn.length;
> +	return length;
>  }
>  
>  static int arch_copy_kprobe(struct kprobe *p)
> 


-- 
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com



  reply	other threads:[~2015-03-10  2:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 11:19 [PATCH] kprobes/x86: Return correct length in __copy_instruction() Eugene Shatokhin
2015-03-10  2:59 ` Masami Hiramatsu [this message]
2015-03-16 15:03   ` Ingo Molnar
2015-03-17  9:45     ` Masami Hiramatsu
2015-04-27 11:03       ` Eugene Shatokhin
2015-05-11 13:47         ` Ingo Molnar

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=54FE5E14.8090303@hitachi.com \
    --to=masami.hiramatsu.pt@hitachi.com \
    --cc=eugene.shatokhin@rosalab.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.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;
as well as URLs for NNTP newsgroup(s).