From: Andi Kleen <andi@firstfloor.org>
To: Ingo Molnar <mingo@elte.hu>,
tglx@linutronix.de, linux-kernel@vger.kernel.org,
torvalds@osdl.org
Subject: [PATCH] Fix direct mapping alias regressin in ioremap v2
Date: Thu, 14 Feb 2008 17:56:45 +0100 [thread overview]
Message-ID: <20080214165645.GA26748@basil.nowhere.org> (raw)
Fix direct mapping alias regressin in ioremap v2
[This fixes the general ioremap bug I mentioned earlier. It was
fortunately easier to fix that I thought first.]
set_memory_*/cpa is not currently able to resolve ioremap addresses to
their direct mapping aliases.
However uncached ioremap still needs to fix up the direct mapping
to be uncached when the direct mapping happens to overlap
the remapped area. Otherwise there would be a cached mapping
to the uncached ioremap area and that is not allowed in the x86
architecture.
Do this explicitely in ioremap() by passing the direct mapping
address to cpa and ignoring the error if the address wasn't
in the direct mapping.
I also fixed a minor bug I noticed -- need to pass in size + offset,
not just size.
v2: Improve description
Fix bug noticed by Ingo of __va() wrapping on 32bit
Signed-off-by: Andi Kleen <ak@suse.de>
Index: linux/arch/x86/mm/ioremap.c
===================================================================
--- linux.orig/arch/x86/mm/ioremap.c
+++ linux/arch/x86/mm/ioremap.c
@@ -104,6 +104,7 @@ static void __iomem *__ioremap(unsigned
unsigned long pfn, offset, last_addr, vaddr;
struct vm_struct *area;
pgprot_t prot;
+ int err;
/* Don't allow wraparound or zero size */
last_addr = phys_addr + size - 1;
@@ -156,9 +157,16 @@ static void __iomem *__ioremap(unsigned
return NULL;
}
- if (ioremap_change_attr(vaddr, size, mode) < 0) {
- vunmap(area->addr);
- return NULL;
+ /* Fix up the direct mapping for the new cache attributes */
+ if ((phys_addr + size + offset) >> PAGE_SHIFT <= max_pfn_mapped) {
+ err = ioremap_change_attr((unsigned long)__va(phys_addr),
+ size + offset, mode);
+ if (err == -EINVAL) {
+ /* Original address was partly unmapped. Ignore. */
+ } else if (err < 0) {
+ vunmap(area->addr);
+ return NULL;
+ }
}
return (void __iomem *) (vaddr + offset);
next reply other threads:[~2008-02-14 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 16:56 Andi Kleen [this message]
2008-02-14 17:42 ` [PATCH] Fix direct mapping alias regressin in ioremap v2 Ingo Molnar
2008-02-14 21:34 ` Andi Kleen
2008-02-14 23:56 ` Ingo Molnar
2008-02-15 8:44 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080214165645.GA26748@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox