@mate I agree with that concern w.r.t. sending random pe binaries to
linux code path.
Separately in Mantic we are reverting zimg boot image format. Kernel
itself fails to kexec it correctly. And mantic kexec tools do not
support this image format correctly. Thus at this point grub 2.12 has
best support for this anyway. And kernel itself & kexec-tools need work.
If/when this gets re-enabled again, breaks will be used to ensure that
grub2 of better than 2.12 is desired to get this going again, likely in
24.04.
** Changed in: linux (Ubuntu)
Milestone: None => later
** Changed in: linux (Ubuntu Focal)
Status: New => Invalid
** Changed in: linux (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux (Ubuntu Lunar)
Status: New => Invalid
** Changed in: grub2-unsigned (Ubuntu Focal)
Status: New => Invalid
** Changed in: grub2-unsigned (Ubuntu Jammy)
Status: New => Invalid
** Changed in: grub2-unsigned (Ubuntu Lunar)
Status: New => Invalid
** Changed in: grub2 (Ubuntu Focal)
Status: New => Invalid
** Changed in: grub2 (Ubuntu Jammy)
Status: New => Invalid
** Changed in: grub2 (Ubuntu Lunar)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2002226
Title:
Add support for kernels compiled with CONFIG_EFI_ZBOOT
Status in grub2 package in Ubuntu:
Fix Released
Status in grub2-unsigned package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Triaged
Status in grub2 source package in Focal:
Invalid
Status in grub2-unsigned source package in Focal:
Invalid
Status in linux source package in Focal:
Invalid
Status in grub2 source package in Jammy:
Invalid
Status in grub2-unsigned source package in Jammy:
Invalid
Status in linux source package in Jammy:
Invalid
Status in grub2 source package in Lunar:
Invalid
Status in grub2-unsigned source package in Lunar:
Invalid
Status in linux source package in Lunar:
Invalid
Bug description:
[Impact]
Arm64 kernels compiled with CONFIG_EFI_ZBOOT=y don't use the
ARM64_IMAGE_MAGIC ('ARM\x64') but LINUX_PE_MAGIC (0x818223cd) in the PE Header.
Our GRUB fails to boot such a kernel.
We should eliminate the following check:
grub-core/loader/efi/linux.c:75:
if (lh->magic != GRUB_LINUX_ARCH_MAGIC_SIGNATURE)
return grub_error(GRUB_ERR_BAD_OS, "invalid magic number");
This will allow any EFI binary to be run using the linux command.
[Test plan]
* check that grub and EFI based ARM64 machines boot
* check that MAAS deployment works
[Where problems could occur]
* Non-EFI bootloaders want to boot with regular vmlinuz.gz. If one is using
piboot, u-boot, abootimg likely one still wants to build Image.gz and have
CONFIG_EFI_ZBOOT disabled.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2002226/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
