Re: [PATCH 1/2] x86/boot: robustify calling startup_{32,64}() from the decompressor code

[Alexander Lobakin]

From: Jiri Slaby <jirislaby@xxxxxxxxxx>
Date: Tue, 1 Nov 2022 07:50:04 +0100

> On 01. 11. 22, 7:47, Jiri Slaby wrote:
> > Tested-by: Jiri Slaby <jirislaby@xxxxxxxxxx>
>
> 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