Re: [PATCH 1/3] kern/efi/mm: Change grub_efi_mm_add_regions() to keep track of map allocation size

On Wed, Jun 12, 2024 at 04:10:49PM +0100, Mate Kukri wrote: > If the map was too big for the initial allocation, it was freed and replaced > with a bigger one, but the free call still used the hard-coded size. > > Seems like this wasn't hit for a long time, because most firmware maps > fit into

[PATCH 1/3] kern/efi/mm: Change grub_efi_mm_add_regions() to keep track of map allocation size

If the map was too big for the initial allocation, it was freed and replaced with a bigger one, but the free call still used the hard-coded size. Seems like this wasn't hit for a long time, because most firmware maps fit into 12K. This bug was trigerred on Project Mu firmware with a big memory