mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH master 4/5] efi: payload: reinstate error message when booting non-EFI stubbed kernel
Date: Fri,  7 Nov 2025 15:17:21 +0100	[thread overview]
Message-ID: <20251107141725.2590394-4-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20251107141725.2590394-1-a.fatoum@pengutronix.de>

With the introduction of filetype_x86_linux_image, we never detect a
filetype_mbr, but instead filetype_x86_linux_image.

Now that we have filetype_x86_efi_linux_image, we can fix this handler
by matching against the distinct filetype_x86_linux_image.

Fixes: 7b0cedb9ddb4 ("efi: payload: split image handling from legacy
                      handover boot and add linux x86 image filetype")
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 efi/payload/image.c | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/efi/payload/image.c b/efi/payload/image.c
index e4e2d26463da..ea6033edc363 100644
--- a/efi/payload/image.c
+++ b/efi/payload/image.c
@@ -165,24 +165,24 @@ static struct binfmt_hook binfmt_efi_hook = {
 	.hook = efi_execute,
 };
 
-static int do_bootm_mbr(struct image_data *data)
+static struct image_handler non_efi_handle_linux_x86;
+
+static int do_bootm_nonefi(struct image_data *data)
 {
-	/* On x86, Linux kernel images have a MBR magic at the end of
-	 * the first 512 byte sector and a PE magic if they're EFI-stubbed.
-	 * The PE magic has precedence over the MBR, so if we arrive in
-	 * this boot handler, the kernel has no EFI stub.
-	 *
-	 * Print a descriptive error message instead of "no image handler
-	 * found for image type MBR sector".
+	/* On x86, Linux kernel images have a bzImage header as well as
+	 * a PE magic if they're EFI-stubbed.
+	 * We have separate file types for x86 Linux images with and
+	 * without PE.
 	 */
-	pr_err("Can't boot MBR sector: Is CONFIG_EFI_STUB disabled in your Linux kernel config?\n");
+	pr_err("'%s' unsupported: CONFIG_EFI_STUB must be enabled in your Linux kernel config\n",
+	       non_efi_handle_linux_x86.name);
 	return -ENOSYS;
 }
 
 static struct image_handler non_efi_handle_linux_x86 = {
 	.name = "non-EFI x86 Linux Image",
-	.bootm = do_bootm_mbr,
-	.filetype = filetype_mbr,
+	.bootm = do_bootm_nonefi,
+	.filetype = filetype_x86_linux_image,
 };
 
 static struct binfmt_hook binfmt_arm64_efi_hook = {
-- 
2.47.3




  parent reply	other threads:[~2025-11-07 14:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-07 14:17 [PATCH master 1/5] efi: payload: drop unreferenced efi_do_execute_image() Ahmad Fatoum
2025-11-07 14:17 ` [PATCH master 2/5] filetype: introduce separate filetype_x86_efi_linux_image Ahmad Fatoum
2025-11-07 14:17 ` [PATCH master 3/5] efi: payload: handover: fix filetype match Ahmad Fatoum
2025-11-07 14:17 ` Ahmad Fatoum [this message]
2025-11-07 14:17 ` [PATCH master 5/5] efi: payload: align kernel boot status messages Ahmad Fatoum
2025-11-10  8:20 ` [PATCH master 1/5] efi: payload: drop unreferenced efi_do_execute_image() Sascha Hauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251107141725.2590394-4-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox