linux-kernel - Re: [tip:efi/core] efibc: Add EFI Bootloader Control module

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]

Date:	Fri, 29 Apr 2016 15:53:39 +0200
From:	jeremy.compostella@...el.com (Compostella, Jeremy)
To:	Matt Fleming <matt@...eblueprint.co.uk>
Cc:	Ingo Molnar <mingo@...nel.org>, <stefan.stanacar@...el.com>,
	<peterz@...radead.org>, <linux-kernel@...r.kernel.org>,
	<tglx@...utronix.de>, <hpa@...or.com>, <bp@...en8.de>,
	<ard.biesheuvel@...aro.org>, <linux-tip-commits@...r.kernel.org>
Subject: Re: [tip:efi/core] efibc: Add EFI Bootloader Control module

Matt Fleming <matt@...eblueprint.co.uk> writes:

> On Fri, 29 Apr, at 01:36:01PM, Jeremy Compostella wrote:
>> I would go for this last proposal because it fixes the issue, it works
>> with the potential race condition you mentioned and it is a simple
>> solution.  Yet, it means that if we really run into a race condition,
>> the LoaderEntryOneShot value might be indeterminate.
>> 
>> Though, this is a very unlikely situation and if it happens I cannot
>> think of any good reason to prefer to store the first restart target
>> or the second.
>> 
>> Do you want me to make this change ?
>
> Yes please, that'd be greatly appreciated. Be sure to do it on top of
> either the EFI 'next' branch or tip:efi/core.
Please, find the patch in attachment.  I wrote it on top of
tip:efi/core.


View attachment "0001-efibc-fix-excessive-stack-footprint-warning.patch" of type "text/x-diff" (2837 bytes)


Jérémy
-- 
One Emacs to rule them all