From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Miroslav Benes <mbenes@suse.cz>,
Nick Desaulniers <ndesaulniers@google.com>,
Julien Thierry <jthierry@redhat.com>,
Kees Cook <keescook@chromium.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] objtool,x86: Additionally decode: mov %rsp, (%reg)
Date: Tue, 9 Feb 2021 10:32:55 -0600 [thread overview]
Message-ID: <20210209163255.epr2gxndsweyfpzi@treble> (raw)
In-Reply-To: <20210209093521.924097404@infradead.org>
On Tue, Feb 09, 2021 at 10:16:02AM +0100, Peter Zijlstra wrote:
> Where we already decode: mov %rsp, %reg, also decode mov %rsp, (%reg).
>
> Nothing should match for this new stack-op.
>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> ---
> tools/objtool/arch/x86/decode.c | 23 ++++++++++++++++++-----
> 1 file changed, 18 insertions(+), 5 deletions(-)
>
> --- a/tools/objtool/arch/x86/decode.c
> +++ b/tools/objtool/arch/x86/decode.c
> @@ -222,14 +222,24 @@ int arch_decode_instruction(const struct
> break;
>
> case 0x89:
> - if (rex_w && !rex_r && modrm_mod == 3 && modrm_reg == 4) {
> + if (rex_w && !rex_r && modrm_reg == 4) {
>
> - /* mov %rsp, reg */
> + /* mov %rsp, */
> ADD_OP(op) {
> op->src.type = OP_SRC_REG;
> op->src.reg = CFI_SP;
> - op->dest.type = OP_DEST_REG;
> - op->dest.reg = op_to_cfi_reg[modrm_rm][rex_b];
> + if (modrm_mod == 3) {
> +
> + /* mov %rsp, reg */
> + op->dest.type = OP_DEST_REG;
> + op->dest.reg = op_to_cfi_reg[modrm_rm][rex_b];
> +
> + } else if (modrm_mod == 0) {
> +
> + /* mov %rsp, (%reg) */
> + op->dest.type = OP_DEST_REG_INDIRECT;
> + op->dest.reg = op_to_cfi_reg[modrm_rm][rex_b];
> + }
What if modrm_mod is 1 or 2? Should 'if' below the 'case' make sure
it's 0 or 3?
> }
> break;
> }
> @@ -259,8 +269,10 @@ int arch_decode_instruction(const struct
> op->dest.reg = CFI_BP;
> op->dest.offset = insn.displacement.value;
> }
> + break;
> + }
>
> - } else if (rex_w && !rex_b && modrm_rm == 4 && sib == 0x24) {
> + if (rex_w && !rex_b && modrm_rm == 4 && sib == 0x24) {
>
> /* mov reg, disp(%rsp) */
> ADD_OP(op) {
> @@ -270,6 +282,7 @@ int arch_decode_instruction(const struct
> op->dest.reg = CFI_SP;
> op->dest.offset = insn.displacement.value;
> }
> + break;
> }
>
> break;
>
Did this change have a point?
--
Josh
next prev parent reply other threads:[~2021-02-09 16:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 9:16 [PATCH v2 0/3] objtool: Support the stack swizzle Peter Zijlstra
2021-02-09 9:16 ` [PATCH v2 1/3] x86/unwind/orc: Change REG_SP_INDIRECT Peter Zijlstra
2021-02-09 9:16 ` [PATCH v2 2/3] objtool,x86: Additionally decode: mov %rsp, (%reg) Peter Zijlstra
2021-02-09 16:32 ` Josh Poimboeuf [this message]
2021-02-09 16:42 ` Peter Zijlstra
2021-02-10 9:08 ` [PATCH v2.1 " Peter Zijlstra
2021-02-10 9:31 ` Peter Zijlstra
2021-02-09 9:16 ` [PATCH v2 3/3] objtool: Support stack-swizzle Peter Zijlstra
2021-02-09 10:35 ` Peter Zijlstra
2021-02-09 15:45 ` [PATCH v2 0/3] objtool: Support the stack swizzle Miroslav Benes
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=20210209163255.epr2gxndsweyfpzi@treble \
--to=jpoimboe@redhat.com \
--cc=jthierry@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.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®