From: Oleg Nesterov <oleg@redhat.com>
To: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Jim Keniston <jkenisto@us.ibm.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uprobes/x86: fix rip-relative handling of EVEX-encoded insns.
Date: Thu, 11 Aug 2016 19:39:21 +0200 [thread overview]
Message-ID: <20160811173921.GB31803@redhat.com> (raw)
In-Reply-To: <20160811154521.20469-1-dvlasenk@redhat.com>
Well, I guess I have to reply...
So let me say that I am not going to even try to review this change. I know
absolutely nothing about x86 insn decoding, but I tend to trust Denys in
this area.
On 08/11, Denys Vlasenko wrote:
>
> Since instruction decoder now supports EVEX-encoded insns, two fixes are needed
> to correctly handle them in uprobes.
>
> Extended bits for MODRM.rm field need to be sanitized just like we do it
> for VEX3, to avoid encoding wrong register for register-relative access.
> EVEX has _two_ extended bits: b and x. Theoretically, EVEX.x should be
> ignored by CPU (since GPRs go only up to 15, not 31), but let's be paranoid
> here: proper encoding for register-relative access should have EVEX.x = 1.
>
> Secondly, we should fetch vex.vvvv for EVEX too.
> This is now super easy because insn decoder populates vex_prefix.bytes[2]
> for all flavors of (e)vex encodings, even for vex2.
>
> Signed-off-by: Denys Vlasenko <dvlasenk@redhat.com>
> CC: Jim Keniston <jkenisto@us.ibm.com>
> CC: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
> CC: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
> CC: Ingo Molnar <mingo@kernel.org>
> CC: Oleg Nesterov <oleg@redhat.com>
> CC: x86@kernel.org
> CC: linux-kernel@vger.kernel.org
> ---
> arch/x86/kernel/uprobes.c | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/arch/x86/kernel/uprobes.c b/arch/x86/kernel/uprobes.c
> index 6c1ff31..a6e6096 100644
> --- a/arch/x86/kernel/uprobes.c
> +++ b/arch/x86/kernel/uprobes.c
> @@ -357,20 +357,22 @@ static void riprel_analyze(struct arch_uprobe *auprobe, struct insn *insn)
> *cursor &= 0xfe;
> }
> /*
> - * Similar treatment for VEX3 prefix.
> - * TODO: add XOP/EVEX treatment when insn decoder supports them
> + * Similar treatment for VEX3/EVEX prefix.
> + * TODO: add XOP treatment when insn decoder supports them
> */
> - if (insn->vex_prefix.nbytes == 3) {
> + if (insn->vex_prefix.nbytes >= 3) {
> /*
> * vex2: c5 rvvvvLpp (has no b bit)
> * vex3/xop: c4/8f rxbmmmmm wvvvvLpp
> * evex: 62 rxbR00mm wvvvv1pp zllBVaaa
> - * (evex will need setting of both b and x since
> - * in non-sib encoding evex.x is 4th bit of MODRM.rm)
> - * Setting VEX3.b (setting because it has inverted meaning):
> + * Setting VEX3.b (setting because it has inverted meaning).
> + * Setting EVEX.x since (in non-SIB encoding) EVEX.x
> + * is the 4th bit of MODRM.rm, and needs the same treatment.
> + * For VEX3-encoded insns, VEX3.x value has no effect in
> + * non-SIB encoding, the change is superfluous but harmless.
> */
> cursor = auprobe->insn + insn_offset_vex_prefix(insn) + 1;
> - *cursor |= 0x20;
> + *cursor |= 0x60;
> }
>
> /*
> @@ -415,12 +417,10 @@ static void riprel_analyze(struct arch_uprobe *auprobe, struct insn *insn)
>
> reg = MODRM_REG(insn); /* Fetch modrm.reg */
> reg2 = 0xff; /* Fetch vex.vvvv */
> - if (insn->vex_prefix.nbytes == 2)
> - reg2 = insn->vex_prefix.bytes[1];
> - else if (insn->vex_prefix.nbytes == 3)
> + if (insn->vex_prefix.nbytes)
> reg2 = insn->vex_prefix.bytes[2];
> /*
> - * TODO: add XOP, EXEV vvvv reading.
> + * TODO: add XOP vvvv reading.
> *
> * vex.vvvv field is in bits 6-3, bits are inverted.
> * But in 32-bit mode, high-order bit may be ignored.
> --
> 2.9.2
>
next prev parent reply other threads:[~2016-08-11 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 15:45 [PATCH] uprobes/x86: fix rip-relative handling of EVEX-encoded insns Denys Vlasenko
2016-08-11 17:39 ` Oleg Nesterov [this message]
2016-08-11 22:13 ` Masami Hiramatsu
2016-08-12 5:39 ` Srikar Dronamraju
2016-08-12 13:45 ` Denys Vlasenko
2016-08-12 8:27 ` [tip:perf/urgent] uprobes/x86: Fix RIP-relative handling of EVEX-encoded instructions tip-bot for Denys Vlasenko
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=20160811173921.GB31803@redhat.com \
--to=oleg@redhat.com \
--cc=dvlasenk@redhat.com \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=srikar@linux.vnet.ibm.com \
--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