linux-kernel - Re: [PATCH 0/9] x86 EFI boot stub

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: <4E43D3AE.70901@gmail.com>
Date:	Thu, 11 Aug 2011 15:05:50 +0200
From:	Maarten Lankhorst <m.b.lankhorst@...il.com>
To:	Matt Fleming <matt@...sole-pimps.org>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/9] x86 EFI boot stub

On 08/11/2011 12:59 PM, Matt Fleming wrote:
> From: Matt Fleming <matt.fleming@...el.com>
>
> This series adds support for an EFI boot stub, similar to the existing
> BIOS boot stub. The result is that you can boot a bzImage on an EFI
> machine without the use of a boot loader by making the bzImage appear
> to the EFI firmware to be an EFI application. Also, a single bzImage
> can be booted on either a BIOS or EFI machine.
>
> Using the EFI boot stub has the advantage that the kernel is
> responsible for configuring the machine to the point where we can
> fully boot the kernel, so we are no longer at the mercy of the boot
> loader.
>
Fails to boot here. I thought changing characteristics from 0x60500020 to 0xe0500020 would help, but no. :/
This change would make the code section writable.

FileAlignment you use is probably wrong, I think it should be 0x200 not 0x2000 .

Maybe you need to add a data section and fix SizeOfInitializedData too?

It just hangs on a blinking cursor, no idea if it actually started executing anything yet or not, since nothing is printed out.

~Maarten

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/