linux-kernel - Re: [PATCH] x86, efi: Calling __pa() with an ioremap'd address is invalid

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: <df88dc7c-e404-4190-a15c-4c3ef44ed45f@email.android.com>
Date:	Tue, 11 Oct 2011 08:45:38 -0700
From:	"hpanvin@...il.com" <hpa@...or.com>
To:	Matt Fleming <matt@...sole-pimps.org>,
	Matthew Garrett <mjg59@...f.ucam.org>
CC:	linux-kernel@...r.kernel.org, x86@...nel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <ming@...e.hu>, Zhang Rui <rui.zhang@...el.com>,
	Huang Ying <huang.ying.caritas@...il.com>
Subject: Re: [PATCH] x86, efi: Calling __pa() with an ioremap'd address is invalid

I think ioremap_cache() should work for either.

Matt Fleming <matt@...sole-pimps.org> wrote:

>On Tue, 2011-10-11 at 14:03 +0100, Matthew Garrett wrote:
>> Is there any chance of unifying the 32 and 64-bit code here as well?
>
>I was under the impression that this wasn't possible for the cached
>case
>because the 32-bit code path uses ioremap_cache() whereas 64-bit uses
>init_memory_mapping() and __va().
>
>Unless I'm missing something?

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
--
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/