linux-kernel - Re: [PATCH] x86, efi: Convert efi_phys_get

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]

Message-ID: <1320665471.3572.110.camel@mfleming-mobl1.ger.corp.intel.com>
Date:	Mon, 07 Nov 2011 11:31:11 +0000
From:	Matt Fleming <matt@...sole-pimps.org>
To:	linux-kernel@...r.kernel.org
Cc:	Matthew Garrett <mjg@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	x86@...nel.org, Zhang Rui <rui.zhang@...el.com>
Subject: Re: [PATCH] x86, efi: Convert efi_phys_get_time() args to physical
 addresses

On Tue, 2011-10-11 at 11:52 +0100, Matt Fleming wrote:
> From: Maurice Ma <maurice.ma@...el.com>
> 
> Because callers of efi_phys_get_time() pass virtual stack addresses as
> arguments, we need to find their corresponding physical addresses and
> when calling GetTime() in physical mode.
> 
> Without this patch the following line is printed on boot,
> 
> 	"Oops: efitime: can't read time!"
> 
> Cc: Matthew Garrett <mjg@...hat.com>
> Cc: Thomas Gleixner <tglx@...utronix.de>
> Cc: Ingo Molnar <mingo@...e.hu>
> Cc: "H. Peter Anvin" <hpa@...or.com>
> Cc: x86@...nel.org
> Cc: Zhang Rui <rui.zhang@...el.com>
> Signed-off-by: Maurice Ma <maurice.ma@...el.com>
> Signed-off-by: Matt Fleming <matt.fleming@...el.com>
> ---
>  arch/x86/platform/efi/efi.c |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)

Ping?


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