From: Randy Dunlap <rdunlap@infradead.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: akpm@linux-foundation.org, broonie@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-next@vger.kernel.org, mhocko@suse.cz,
mm-commits@vger.kernel.org, sfr@canb.auug.org.au,
Josh Poimboeuf <jpoimboe@redhat.com>
Subject: Re: mmotm 2020-05-05-15-28 uploaded (objtool warning)
Date: Fri, 8 May 2020 10:28:20 -0700 [thread overview]
Message-ID: <73dd7a8c-87a4-695d-6f3b-ddde337c0747@infradead.org> (raw)
In-Reply-To: <20200508103830.GZ5298@hirez.programming.kicks-ass.net>
On 5/8/20 3:38 AM, Peter Zijlstra wrote:
> On Tue, May 05, 2020 at 10:40:43PM -0700, Randy Dunlap wrote:
>> On 5/5/20 3:29 PM, akpm@linux-foundation.org wrote:
>>> The mm-of-the-moment snapshot 2020-05-05-15-28 has been uploaded to
>>>
>>> http://www.ozlabs.org/~akpm/mmotm/
>>>
>>> mmotm-readme.txt says
>>>
>>> README for mm-of-the-moment:
>>>
>>> http://www.ozlabs.org/~akpm/mmotm/
>>>
>>> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
>>> more than once a week.
>>>
>>
>>
>> on x86_64:
>>
>> arch/x86/hyperv/hv_apic.o: warning: objtool: hv_apic_write()+0x25: alternative modifies stack
>
> Wheee... this seems to have cured it for me.
>
> ---
> Subject: objtool: Allow no-op CFI ops in alternatives
> From: Peter Zijlstra <peterz@infradead.org>
> Date: Fri May 8 12:34:33 CEST 2020
>
> Randy reported a false-positive: "alternative modifies stack".
>
> What happens is that:
>
> alternative_io("movl %0, %P1", "xchgl %0, %P1", X86_BUG_11AP,
> 13d: 89 9d 00 d0 7f ff mov %ebx,-0x803000(%rbp)
>
> decodes to an instruction with CFI-ops because it modifies RBP.
> However, due to this being a !frame-pointer build, that should not in
> fact change the CFI state.
>
> So instead of dis-allowing any CFI-op, verify the op would've actually
> changed the CFI state.
>
> Fixes: 7117f16bf460 ("objtool: Fix ORC vs alternatives")
> Reported-by: Randy Dunlap <rdunlap@infradead.org>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> tools/objtool/check.c | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
> --- a/tools/objtool/check.c
> +++ b/tools/objtool/check.c
> @@ -2078,17 +2078,18 @@ static int handle_insn_ops(struct instru
> struct stack_op *op;
>
> list_for_each_entry(op, &insn->stack_ops, list) {
> + struct cfi_state old_cfi = state->cfi;
> int res;
>
> - if (insn->alt_group) {
> - WARN_FUNC("alternative modifies stack", insn->sec, insn->offset);
> - return -1;
> - }
> -
> res = update_cfi_state(insn, &state->cfi, op);
> if (res)
> return res;
>
> + if (insn->alt_group && memcmp(&state->cfi, &old_cfi, sizeof(struct cfi_state))) {
> + WARN_FUNC("alternative modifies stack", insn->sec, insn->offset);
> + return -1;
> + }
> +
> if (op->dest.type == OP_DEST_PUSHF) {
> if (!state->uaccess_stack) {
> state->uaccess_stack = 1;
>
--
~Randy
prev parent reply other threads:[~2020-05-08 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 22:29 mmotm 2020-05-05-15-28 uploaded akpm
2020-05-06 5:40 ` mmotm 2020-05-05-15-28 uploaded (objtool warning) Randy Dunlap
2020-05-08 10:38 ` Peter Zijlstra
2020-05-08 16:01 ` Josh Poimboeuf
2020-05-08 17:28 ` Randy Dunlap [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=73dd7a8c-87a4-695d-6f3b-ddde337c0747@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).