linux-kernel - Re: 5.10 RC 7: grub2 out of memory

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]

Date:   Mon, 7 Dec 2020 10:38:36 +0100
From:   David Hildenbrand <david@...hat.com>
To:     Elias Carter <edcarter@...berta.ca>, linux-kernel@...r.kernel.org,
        linux-mm@...ck.org
Subject: Re: 5.10 RC 7: grub2 out of memory

On 07.12.20 10:16, Elias Carter wrote:
> I just compiled and installed 5.10 RC 7 and got a message from grub2:
> "out of memory, press any key to continue" shortly followed by a
> kernel panic (see attached screenshot).
> 
> The 5.4.0-56-generic kernel from Ubuntu works on my machine fine.
> 
> Things I have tried so far:
> - setting grub video mode to "console"
> - setting grub video resolution to 800x600
> - regenerating the initramfs for 5.10 RC 7
> - verifying that /boot has free space
> - changing boot mode from UEFI to legacy BIOS
> 
> I have attached the following:
> 1.) dmesg ran from using the 5.4 kernel (since I cant boot into 5.10 RC 7)
> 2.) my 5.10 RC 7 kernel .config
> 3.) screenshot of kernel panic after "out of memory" grub2 message
> 4.) my /etc/default/grub
> 
> Please let me know if you would like any more information or testing of patches.

The kernel crashes because it's unable to mount root - I suspect the
initrd is not loaded, because I would have expected systemd messages
before trying to mount root (after loading additional drivers from the
initrd). I assume grub2 fails to load the (now too big?) initrd - you
could try compiling out debug symbols and give it a try.

What's the size difference between old vs. new kernel and old vs. new
initrd?


Similar report for aarch64 was at

https://bugzilla.redhat.com/show_bug.cgi?id=1615969

which turned out to be a grub2 issue. Which distro/grub2 version etc are
you running?

-- 
Thanks,

David / dhildenb