From: Alexander Lobakin <alexandr.lobakin@intel.com>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: Alexander Lobakin <alexandr.lobakin@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Tony Luck <tony.luck@intel.com>,
Kees Cook <keescook@chromium.org>,
Masahiro Yamada <masahiroy@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] x86/boot: robustify calling startup_{32,64}() from the decompressor code
Date: Tue, 1 Nov 2022 16:38:34 +0100 [thread overview]
Message-ID: <20221101153834.975871-1-alexandr.lobakin@intel.com> (raw)
In-Reply-To: <39ac78ea-1ee5-8911-1208-c56e57df7338@kernel.org>
From: Jiri Slaby <jirislaby@kernel.org>
Date: Tue, 1 Nov 2022 07:50:04 +0100
> On 01. 11. 22, 7:47, Jiri Slaby wrote:
> > Tested-by: Jiri Slaby <jirislaby@kernel.org>
>
> FWIW that means: tested with gcc-lto which deliberately stores
> startup_64() randomly, not to the beginning of vmlinux.
Yeah, you never know. After rebasing on top of 6.1-rc1 my FG-KASLR
series stopped booting, I found out that the combo of that
head-object-list.txt + -ffunction-sections (but for Asm) also made
startup_64() appear in random parts of .head.text.
Re head removal -- that would be awesome, but currently from what
I've tried during the development, there's a lot of stuff to be
redone, the compressor code sometimes just doesn't want to work
if you play with .head.text too much. Will see.
>
> --
> js
> suse labs
Thanks,
Olek
next prev parent reply other threads:[~2022-11-01 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 15:10 [PATCH 0/2] x86/boot: fix relying on link order Alexander Lobakin
2022-10-31 15:10 ` [PATCH 1/2] x86/boot: robustify calling startup_{32,64}() from the decompressor code Alexander Lobakin
2022-10-31 20:31 ` H. Peter Anvin
2022-11-01 15:44 ` Alexander Lobakin
2022-11-01 6:47 ` Jiri Slaby
2022-11-01 6:50 ` Jiri Slaby
2022-11-01 15:38 ` Alexander Lobakin [this message]
2022-10-31 15:10 ` [PATCH 2/2] scripts/head-object-list: remove x86 from the list Alexander Lobakin
2022-11-01 6:39 ` Jiri Slaby
2022-10-31 15:20 ` [PATCH 0/2] x86/boot: fix relying on link order Borislav Petkov
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=20221101153834.975871-1-alexandr.lobakin@intel.com \
--to=alexandr.lobakin@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jirislaby@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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 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.