linux-kernel - Re: [PATCH] Fix e820 end address with EFI

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, 01 Mar 2009 13:44:54 -0500
From:	Brian Maly <bmaly@...hat.com>
To:	Yinghai Lu <yinghai@...nel.org>
CC:	Ingo Molnar <mingo@...e.hu>, Huang Ying <ying.huang@...el.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Fix e820 end address with EFI

With the kernel that now boots (when max_pfn is set to = last e820 address regardless of type), efi_enter_virtual_mode() does not call efi_ioremap(). Maybe efi_ioremap() is what needs fixing? I should mention this is a regression. 2.6.26 worked, 2.6.27 does not, and seems like things stopped working in 2.6.26-git1. I will check to see if efi_ioremap() used to be called with a 2.6.26 kernel on this hardware and see where the mapped addresses were. Maybe I can verify efi_ioremap() is actually broken.

Brian

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