From: Borislav Petkov <bp@suse.de>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-efi <linux-efi@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Thadeu Lima de Souza Cascardo <cascardo@canonical.com>,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@kernel.org>
Subject: Re: [PATCH] efi/x86-mixed: leave RET unmitigated but move it into .rodata
Date: Sun, 24 Jul 2022 21:17:44 +0200 [thread overview]
Message-ID: <Yt2a2P69i8pHRO97@zn.tnic> (raw)
In-Reply-To: <CAMj1kXEM2tXxCqcjDDNSS_OHsnJ1XTDNWBGdfFc-4zKJKpkTXg@mail.gmail.com>
On Sun, Jul 24, 2022 at 08:34:36PM +0200, Ard Biesheuvel wrote:
> Are you sure you fixed up the conflict correctly? It seems the
> __efi64_thunk end marker ends up in .rodata in your case.
Yep, I f*cked up the merge even if it was pretty easy in meld - sorry
about that.
Now it is correct but it complains differently:
vmlinux.o: warning: objtool: efi_thunk_query_variable_info_nonblocking+0x1ba: unreachable instruction
$ ./scripts/faddr2line vmlinux.o efi_thunk_query_variable_info_nonblocking+0x1ba
efi_thunk_query_variable_info_nonblocking+0x1ba/0x330:
efi_thunk_query_variable_info_nonblocking at /home/boris/kernel/linux/arch/x86/platform/efi/efi_64.c:787
(inlined by) efi_thunk_query_variable_info_nonblocking at /home/boris/kernel/linux/arch/x86/platform/efi/efi_64.c:769
and looking at the asm, it points to:
# 0 "" 2
#NO_APP
movq efi(%rip), %rax # efi.runtime, efi.runtime
movl 12(%rsp), %r8d # %sfp, prephitmp_87
leaq 16(%rsp), %r9 #,
movl %r15d, %ecx # _104,
movl %r14d, %edx # _95,
movl %ebp, %esi # attr,
movl 76(%rax), %edi # _30->mixed_mode.query_variable_info, _30->mixed_mode.query_variable_info
call __efi64_thunk #
#APP
# 787 "arch/x86/platform/efi/efi_64.c" 1
1: movl %r12d,%ds # __val <---
this here, after the __efi64_thunk call, which is that segment restoring
after the __efi_thunk call:
loadsegment(ds, __ds);
Weird, I don't see why though - that should be reachable.
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman
(HRB 36809, AG Nürnberg)
prev parent reply other threads:[~2022-07-24 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 16:06 [PATCH] efi/x86-mixed: leave RET unmitigated but move it into .rodata Ard Biesheuvel
2022-07-23 17:20 ` Linus Torvalds
2022-07-24 8:39 ` Ard Biesheuvel
2022-07-24 17:27 ` Borislav Petkov
2022-07-24 18:34 ` Ard Biesheuvel
2022-07-24 19:17 ` Borislav Petkov [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=Yt2a2P69i8pHRO97@zn.tnic \
--to=bp@suse.de \
--cc=ardb@kernel.org \
--cc=cascardo@canonical.com \
--cc=jpoimboe@kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.