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 13:16:35 +0100
From:	Matt Fleming <matt@...eblueprint.co.uk>
To:	"Compostella, Jeremy" <jeremy.compostella@...el.com>
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

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.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ