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:	Thu, 13 Jan 2011 09:16:26 -0800
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Matthew Garrett <mjg@...hat.com>
Cc:	Takao Indoh <indou.takao@...fujitsu.com>,
	Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>,
	horms@...ge.net.au, nhorman@...driver.com,
	kexec@...ts.infradead.org, linux-kernel@...r.kernel.org,
	mingo@...hat.com, hpa@...or.com, tglx@...utronix.de,
	vgoyal@...hat.com
Subject: Re: [PATCH v2][EFI] Run EFI in physical mode

Matthew Garrett <mjg@...hat.com> writes:

> We're seeing issues with some Dell hardware when EFI is run in physical 
> mode - it seems that Windows uses virtual mode, so the physical path is 
> never exercised. I'm not sure that changing the default to physical is 
> going to be possible without compatibility issues.

The bootloaders use physical mode, and there shouldn't be a separate
physical vs virtual mode.  It should be the same code with or without
relocations applied.  At worst we can set virtual address to the
physical address, on buggy boards.

Honestly if the problem is the EFI code is so buggy we can't use it
in physical mode the answer is almost certainly not to use the
buggy EFI code.

The only bits that I don't think have an alternative are the firmware
variable accesses.   Which are a nice to have, but not a show stopper
anywhere.

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