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: Mon, 21 Sep 2020 10:12:26 -0500 [thread overview]
Message-ID: <20200921151226.3ismmtndjn4t5z4a@treble> (raw)
In-Reply-To: <249188d0-d65e-c862-7cb9-7e1db05361c6@redhat.com>
On Mon, Sep 21, 2020 at 11:31:28AM +0100, Julien Thierry wrote:
> > > 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 ?
> >
>
> Does it matter? My unstandig was that the register used to point to the CFA
> is getting overwritten, so we need to fallback to something known which is
> the offset from the stack pointer.
>
> Was that not the case?
Maybe. I was wondering if it would be possible to overwrite the stack
pointer, like 'mov disp(%rsp), %rsp', which could be possible in asm.
Though I suppose the below code would be harmless, since the CFA
base/offset would already be CFI_SP/cfi->stack_size respectively.
Still, no harm in making the condition more precise.
> > > +
> > > + /* mov disp(%rsp), %rbp */
> > > + cfa->base = CFI_SP;
> > > + cfa->offset = cfi->stack_size;
> > > + }
--
Josh
prev parent reply other threads:[~2020-09-21 15:12 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
2020-09-21 10:31 ` Julien Thierry
2020-09-21 15:12 ` Josh Poimboeuf [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=20200921151226.3ismmtndjn4t5z4a@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®