From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Chuang Wang <nashuiliang@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alex Deucher <alexander.deucher@amd.com>,
"Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/kprobes: Use switch-case for 0xFF opcodes in prepare_emulation
Date: Wed, 30 Nov 2022 22:38:14 +0900 [thread overview]
Message-ID: <20221130223814.667999640ad298f843c2aaf2@kernel.org> (raw)
In-Reply-To: <20221129084022.718355-1-nashuiliang@gmail.com>
On Tue, 29 Nov 2022 16:39:51 +0800
Chuang Wang <nashuiliang@gmail.com> wrote:
> For the `FF /digit` opcodes in prepare_emulation, use switch-case
> instead of hand-written code to make the logic easier to understand.
>
> Signed-off-by: Chuang Wang <nashuiliang@gmail.com>
This looks good to me.
Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Thank you!
> ---
> arch/x86/kernel/kprobes/core.c | 20 +++++++++++---------
> 1 file changed, 11 insertions(+), 9 deletions(-)
>
> diff --git a/arch/x86/kernel/kprobes/core.c b/arch/x86/kernel/kprobes/core.c
> index 66299682b6b7..66ec32b6cd0e 100644
> --- a/arch/x86/kernel/kprobes/core.c
> +++ b/arch/x86/kernel/kprobes/core.c
> @@ -655,17 +655,19 @@ static int prepare_emulation(struct kprobe *p, struct insn *insn)
> * is determined by the MOD/RM byte.
> */
> opcode = insn->modrm.bytes[0];
> - if ((opcode & 0x30) == 0x10) {
> - if ((opcode & 0x8) == 0x8)
> - return -EOPNOTSUPP; /* far call */
> - /* call absolute, indirect */
> + switch (X86_MODRM_REG(opcode)) {
> + case 0b010: /* FF /2, call near, absolute indirect */
> p->ainsn.emulate_op = kprobe_emulate_call_indirect;
> - } else if ((opcode & 0x30) == 0x20) {
> - if ((opcode & 0x8) == 0x8)
> - return -EOPNOTSUPP; /* far jmp */
> - /* jmp near absolute indirect */
> + break;
> + case 0b100: /* FF /4, jmp near, absolute indirect */
> p->ainsn.emulate_op = kprobe_emulate_jmp_indirect;
> - } else
> + break;
> + case 0b011: /* FF /3, call far, absolute indirect */
> + case 0b101: /* FF /5, jmp far, absolute indirect */
> + return -EOPNOTSUPP;
> + }
> +
> + if (!p->ainsn.emulate_op)
> break;
>
> if (insn->addr_bytes != sizeof(unsigned long))
> --
> 2.37.2
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2022-11-30 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 8:39 Chuang Wang
2022-11-30 13:38 ` Masami Hiramatsu [this message]
2023-01-10 12:03 ` [tip: perf/core] " tip-bot2 for Chuang Wang
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=20221130223814.667999640ad298f843c2aaf2@kernel.org \
--to=mhiramat@kernel.org \
--cc=alexander.deucher@amd.com \
--cc=bp@alien8.de \
--cc=broonie@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nashuiliang@gmail.com \
--cc=peterz@infradead.org \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®