linux-kernel - Re: [RFC][PATCH 1/1] x86, efi: EFI boot stub config file support

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4F690314.3080601@shealevy.com>
Date:	Tue, 20 Mar 2012 18:22:12 -0400
From:	Shea Levy <shea@...alevy.com>
To:	linux-kernel@...r.kernel.org
CC:	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
	Matt Fleming <matt.fleming@...el.com>,
	Maarten Lankhorst <m.b.lankhorst@...il.com>
Subject: Re: [RFC][PATCH 1/1] x86, efi: EFI boot stub config file support

On 03/18/2012 11:49 AM, Shea Levy wrote:
> On 3/18/12 11:45 AM, Shea Levy wrote:
>> Hello,
>>
>> Inlined is a patch to have the kernel read its parameters from a
>> config file when booted via the EFI boot stub without any parameters
>> passed. This patch roughly follows the plan I discussed when
>> proposing this idea, except now the file is found relative to the
>> location of the bzImage and there is no additional check to see if
>> image->parent_handle is NULL (despite the spec saying it will be NULL
>> when the image was loaded by the firmware itself, it was never NULL
>> on any of the systems I tested).
>>
>> Cheers,
>> Shea Levy

I haven't yet gotten a reply to this, should I wait until after the 
merge window and resubmit it then?

~Shea
--
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/