From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Julien Thierry <jthierry@redhat.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
mbenes@suse.cz, raphael.gault@arm.com, benh@kernel.crashing.org
Subject: Re: [PATCH 3/3] objtool: check: Make SP memory operation match PUSH/POP semantics
Date: Fri, 18 Sep 2020 16:43:18 -0500 [thread overview]
Message-ID: <20200918214318.2d7msla53ysxkbaz@treble> (raw)
In-Reply-To: <20200915081204.9204-4-jthierry@redhat.com>
On Tue, Sep 15, 2020 at 09:12:04AM +0100, Julien Thierry wrote:
> Architectures without PUSH/POP instructions will always access the stack
> though memory operations (SRC/DEST_INDIRECT). Make those operations have
> the same effect on the CFA as PUSH/POP, with no stack pointer
> modification.
>
> Signed-off-by: Julien Thierry <jthierry@redhat.com>
> ---
> tools/objtool/check.c | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/tools/objtool/check.c b/tools/objtool/check.c
> index f45991c2db41..7ff87fa3caec 100644
> --- a/tools/objtool/check.c
> +++ b/tools/objtool/check.c
> @@ -2005,6 +2005,13 @@ static int update_cfi_state(struct instruction *insn, struct cfi_state *cfi,
> break;
>
> case OP_SRC_REG_INDIRECT:
> + if (!cfi->drap && op->dest.reg == cfa->base) {
&& op->dest.reg == CFI_BP ?
> +
> + /* mov disp(%rsp), %rbp */
> + cfa->base = CFI_SP;
> + cfa->offset = cfi->stack_size;
> + }
> +
> if (cfi->drap && op->src.reg == CFI_BP &&
> op->src.offset == cfi->drap_offset) {
>
> @@ -2026,6 +2033,11 @@ static int update_cfi_state(struct instruction *insn, struct cfi_state *cfi,
> /* mov disp(%rbp), %reg */
> /* mov disp(%rsp), %reg */
> restore_reg(cfi, op->dest.reg);
> + } else if (op->src.reg == CFI_SP &&
An empty line above the else would help readability.
> + op->src.offset == regs[op->dest.reg].offset + cfi->stack_size) {
> +
> + /* mov disp(%rsp), %reg */
> + restore_reg(cfi, op->dest.reg);
> }
>
> break;
> @@ -2103,6 +2115,11 @@ static int update_cfi_state(struct instruction *insn, struct cfi_state *cfi,
> /* mov reg, disp(%rsp) */
> save_reg(cfi, op->src.reg, CFI_CFA,
> op->dest.offset - cfi->cfa.offset);
> + } else if (op->dest.reg == CFI_SP) {
Same here.
> +
> + /* mov reg, disp(%rsp) */
> + save_reg(cfi, op->src.reg, CFI_CFA,
> + op->dest.offset - cfi->stack_size);
> }
>
> break;
> --
> 2.21.3
>
--
Josh
next prev parent reply other threads:[~2020-09-18 21:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 8:12 [PATCH 0/3] objtool: Extend CFA updating/checking Julien Thierry
2020-09-15 8:12 ` [PATCH 1/3] objtool: check: Fully validate the stack frame Julien Thierry
2020-09-18 20:56 ` Josh Poimboeuf
2020-09-21 10:31 ` Julien Thierry
2020-09-21 15:03 ` Josh Poimboeuf
2020-09-15 8:12 ` [PATCH 2/3] objtool: check: Support addition to set CFA base Julien Thierry
2020-09-18 21:09 ` Josh Poimboeuf
2020-09-15 8:12 ` [PATCH 3/3] objtool: check: Make SP memory operation match PUSH/POP semantics Julien Thierry
2020-09-18 21:43 ` Josh Poimboeuf [this message]
2020-09-21 10:31 ` Julien Thierry
2020-09-21 15:12 ` Josh Poimboeuf
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=20200918214318.2d7msla53ysxkbaz@treble \
--to=jpoimboe@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=jthierry@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=peterz@infradead.org \
--cc=raphael.gault@arm.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
all inboxes | Powered by JetHome®