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: <20110608193833.GA29855@srcf.ucam.org>
Date:	Wed, 8 Jun 2011 20:38:33 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Jim Bos <jim876@...all.nl>, "H. Peter Anvin" <hpa@...ux.intel.com>,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	Maarten Lankhorst <m.b.lankhorst@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Greg KH <gregkh@...e.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: 2.6.39.1 immediately reboots/resets on EFI system

On Wed, Jun 08, 2011 at 12:35:54PM -0700, Yinghai Lu wrote:
> On 06/08/2011 12:29 PM, Matthew Garrett wrote:
> >> what former? you can not fix some corner case by breaking most other cases.
> > 
> > All Dell laptops, all new Apples, some Lenovos, various Intel server 
> > platforms. That I've found so far.
> 
> do you mean before that patch, all those machine will not boot linux kernel with UEFI support?

Correct.

> > And we need to be able to map the boot services code, so we can't put 
> > the kernel on top of it.
> 
> after bootloader, those area should be free already.

That's what the spec says. Reality says differently. We need those 
ranges to be available to the kernel until after SetVirtualAddressMap() 
has been called, which means we need to avoid putting the kernel on top 
of them.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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