From: Masami Hiramatsu <mhiramat@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H . Peter Anvin" <hpa@zytor.com>,
Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
"David S . Miller" <davem@davemloft.net>,
Andrey Ryabinin <aryabinin@virtuozzo.com>
Subject: Re: [RFC PATCH tip/master 8/8] kprobes/x86: Consolidate insn decoder users for copying code
Date: Mon, 27 Mar 2017 07:43:48 +0900 [thread overview]
Message-ID: <20170327074348.567d4043935269b817ae6bf0@kernel.org> (raw)
In-Reply-To: <149049917108.5373.9195034052283489965.stgit@devbox>
On Sun, 26 Mar 2017 12:33:01 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:
> Consolidate x86 instruction decoder users on the path of
> copying original code for kprobes.
>
> Kprobes decodes same instruction 3 times in maximum when
> preparing instruction buffer. The first time for getting the
> length of instruction, the 2nd for adjusting displacement,
> and the 3rd for checking whether the instruction is boostable
> or not. For each time, actually decoding target address is
> slightly different (1st is original address or recovered
> instruction buffer, 2nd and 3rd are copied buffer), but
> basically those must have same instruction.
> Thus, this patch also changes the target address to copied
> buffer at first and reuses the decoded "insn" for displacement
> adjusting and checking boostable.
>
> Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
> ---
> arch/x86/kernel/kprobes/common.h | 4 +-
> arch/x86/kernel/kprobes/core.c | 62 +++++++++++++++++---------------------
> arch/x86/kernel/kprobes/opt.c | 5 ++-
> 3 files changed, 33 insertions(+), 38 deletions(-)
>
> diff --git a/arch/x86/kernel/kprobes/common.h b/arch/x86/kernel/kprobes/common.h
> index d688826..db2182d 100644
> --- a/arch/x86/kernel/kprobes/common.h
> +++ b/arch/x86/kernel/kprobes/common.h
> @@ -67,7 +67,7 @@
> #endif
>
> /* Ensure if the instruction can be boostable */
> -extern int can_boost(kprobe_opcode_t *instruction, void *addr);
> +extern int can_boost(struct insn *insn, void *orig_addr);
> /* Recover instruction if given address is probed */
> extern unsigned long recover_probed_instruction(kprobe_opcode_t *buf,
> unsigned long addr);
> @@ -75,7 +75,7 @@ extern unsigned long recover_probed_instruction(kprobe_opcode_t *buf,
> * Copy an instruction and adjust the displacement if the instruction
> * uses the %rip-relative addressing mode.
> */
> -extern int __copy_instruction(u8 *dest, u8 *src);
> +extern int __copy_instruction(u8 *dest, u8 *src, struct insn *insn);
>
> /* Generate a relative-jump/call instruction */
> extern void synthesize_reljump(void *from, void *to);
> diff --git a/arch/x86/kernel/kprobes/core.c b/arch/x86/kernel/kprobes/core.c
> index a9ae61a..de7475b 100644
> --- a/arch/x86/kernel/kprobes/core.c
> +++ b/arch/x86/kernel/kprobes/core.c
> @@ -164,33 +164,29 @@ static kprobe_opcode_t *skip_prefixes(kprobe_opcode_t *insn)
> NOKPROBE_SYMBOL(skip_prefixes);
>
> /*
> - * Returns non-zero if opcode is boostable.
> + * Returns non-zero if INSN is boostable.
> * RIP relative instructions are adjusted at copying time in 64 bits mode
> */
> -int can_boost(kprobe_opcode_t *opcodes, void *addr)
> +int can_boost(struct insn *insn, void *addr)
> {
> - struct insn insn;
> kprobe_opcode_t opcode;
>
> if (search_exception_tables((unsigned long)addr))
> return 0; /* Page fault may occur on this address. */
>
> - kernel_insn_init(&insn, (void *)opcodes, MAX_INSN_SIZE);
> - insn_get_opcode(&insn);
> -
> /* 2nd-byte opcode */
> - if (insn.opcode.nbytes == 2)
> - return test_bit(insn.opcode.bytes[1],
> + if (insn->opcode.nbytes == 2)
> + return test_bit(insn->opcode.bytes[1],
> (unsigned long *)twobyte_is_boostable);
>
> - if (insn.opcode.nbytes != 1)
> + if (insn.opcode->nbytes != 1)
Oops, here is insn->opcode.nbytes, not insn.opcode->nbytes.
--
Masami Hiramatsu <mhiramat@kernel.org>
prev parent reply other threads:[~2017-03-26 22:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-26 3:23 [RFC PATCH tip/master 0/8] kprobes/x86: Make kprobes instruction buffers read-only Masami Hiramatsu
2017-03-26 3:24 ` [RFC PATCH tip/master 1/8] kprobes/x86: Fix not to boost call far instruction Masami Hiramatsu
2017-03-26 3:25 ` [RFC PATCH tip/master 2/8] kprobes/x86: Fix the description of __copy_instruction() Masami Hiramatsu
2017-03-26 3:27 ` [RFC PATCH tip/master 3/8] kprobes/x86: Use instruction decoder for booster Masami Hiramatsu
2017-03-26 3:28 ` [RFC PATCH tip/master 4/8] kprobes/x86: Do not modify singlestep buffer while resuming Masami Hiramatsu
2017-03-26 3:29 ` [RFC PATCH tip/master 5/8] kprobes/x86: Make boostable flag boolean Masami Hiramatsu
2017-03-26 3:30 ` [RFC PATCH tip/master 6/8] kprobes/x86: Set kprobes pages readonly Masami Hiramatsu
2017-03-26 3:31 ` [RFC PATCH tip/master 7/8] kprobes/x86: Use probe_kernel_read instead of memcpy Masami Hiramatsu
2017-03-26 3:33 ` [RFC PATCH tip/master 8/8] kprobes/x86: Consolidate insn decoder users for copying code Masami Hiramatsu
2017-03-26 22:43 ` 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=20170327074348.567d4043935269b817ae6bf0@kernel.org \
--to=mhiramat@kernel.org \
--cc=ananth@linux.vnet.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=aryabinin@virtuozzo.com \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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