anyway, should i apply this as a separate patch or as an addition to the previous one (the one with bss.efistub addition)?
r. On 3/15/24 18:48, Ard Biesheuvel wrote:
On Fri, 15 Mar 2024 at 17:24, Radek Podgorny <radek@xxxxxxxxxxx> wrote:it's systemd-boot. attaching bootctl output. now looking at it, it seems that while systemd (and systemd-boot) gets timely updates on my system (currently at 255.4), the stub (is this how it's called?) does not get updated automatically in the efi partition (still at version 244?). i can try to update it. but i'll wait for your instructions since this may be some rare situation and we may use it for testing. anyway, i'm compiling new kernel with your suggested changes right now so i'll let you know how it turned out, soon. r. p.s.: ha! nevermind, i just checked the other systems which boot fine and they also are on stub (?) 244 so it's probably not the cause.OK that makes sense. I installed Arch linux in a VM (what a pain!) but I don't think the distro has anything to do with it. I did realize that reverting that patch is not going to be a full solution in any case. Could you please try whether the following fix works for you? --- a/drivers/firmware/efi/libstub/x86-stub.c +++ b/drivers/firmware/efi/libstub/x86-stub.c @@ -473,6 +473,9 @@ int options_size = 0; efi_status_t status; char *cmdline_ptr; + extern char _bss[], _ebss[]; + + memset(_bss, 0, _ebss - _bss); efi_system_table = sys_table_arg;
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature
