linux-kernel - Re: Regression with commit 0a67361dcdaa

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <9ae0c751-5024-6eda-ca78-80cfd1ed066f@linux.intel.com>
Date:   Thu, 16 Apr 2020 17:56:38 +0300
From:   Jarkko Nikula <jarkko.nikula@...ux.intel.com>
To:     Ard Biesheuvel <ardb@...nel.org>
Cc:     linux-efi <linux-efi@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Tony Luck <tony.luck@...el.com>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Subject: Re: Regression with commit 0a67361dcdaa

On 4/16/20 5:36 PM, Ard Biesheuvel wrote:
> On Thu, 16 Apr 2020 at 16:35, Jarkko Nikula
> <jarkko.nikula@...ux.intel.com> wrote:
>>
>> Hi
>>
>> v5.7-rc1 hangs in early boot on an Intel Atom based prototype hardware
>> while v5.6 boots fine. I bisected the regression into 0a67361dcdaa
>> ("efi/x86: Remove runtime table address from kexec EFI setup data").
>>
>> v5.7-rc1 caused a reboot loop on another Intel Core based prototype HW.
>> Reboots also on top of 0a67361dcdaa but boots fine with that commit
>> reverted.
>>
>> Our test system uses kexec to boot the test kernel. These two machines
>> got regression with v5.7-rc1. We have also others that boot fine.
>>
> 
> This should already be fixed in Linus's tree. Please report back
> whether that solves your problem or not.
> 
Ah, I forgot to pull & test before bisecting...

Yes, both machines boot fine with the HEAD 00086336a8d9 ("Merge tag 
'efi-urgent-2020-04-15' of 
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip").

-- 
Jarkko