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:	Sun, 06 Apr 2014 11:40:04 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
	Matthew Garrett <mjg59@...f.ucam.org>
CC:	"Li, Aubrey" <aubrey.li@...ux.intel.com>,
	Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org, rostedt@...dmis.org,
	tglx@...utronix.de, linux-tip-commits@...r.kernel.org,
	Adam Williamson <awilliam@...hat.com>
Subject: Re: [tip:x86/reboot] [PATCH] x86: Try the BIOS reboot method before
 the PCI reboot method

On 04/06/2014 10:40 AM, One Thousand Gnomes wrote:
> On Fri, 4 Apr 2014 16:13:59 +0100
> Matthew Garrett <mjg59@...f.ucam.org> wrote:
> 
>> On Fri, Apr 04, 2014 at 09:38:57PM +0800, Li, Aubrey wrote:
>>
>>> I don't think there is enough justification to revert the patch. We
>>> introduce EFI into the default list, we didn't see any reason to remove
>>> it out so far.
>>
>> We should be using the EFI method, yes. But it seems that CF9 isn't 
>> safe, so we should drop that.
>>
> 
> Windows does not use CF9 and there are known, documented cases where CF9
> will not work reliably. That includes reliable reboot on some Baytrail
> systems. (Erratum VLT60 and VLT62).
> 
> So we really shouldn't be doing 0xCF9 except as a last resort if we are
> still alive and have been through the official reboot methods.
> 

No question. The question at hand is if we should do it after all other
non-terminal (BIOS, triple) methods have been tried.

	-hpa


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ