From: tip-bot for Dave Hansen <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
dave@linux.vnet.ibm.com, tglx@linutronix.de, dave@sr71.net,
penguin-kernel@i-love.sakura.ne.jp
Subject: [tip:x86/urgent] x86: Do not try to sync identity map for non-mapped pages
Date: Thu, 7 Mar 2013 13:59:37 -0800 [thread overview]
Message-ID: <tip-60f583d56aa515b896a9d94f860f52640c1e8a75@git.kernel.org> (raw)
In-Reply-To: <20130307163151.D9B58C4E@kernel.stglabs.ibm.com>
Commit-ID: 60f583d56aa515b896a9d94f860f52640c1e8a75
Gitweb: http://git.kernel.org/tip/60f583d56aa515b896a9d94f860f52640c1e8a75
Author: Dave Hansen <dave@sr71.net>
AuthorDate: Thu, 7 Mar 2013 08:31:51 -0800
Committer: H. Peter Anvin <hpa@zytor.com>
CommitDate: Thu, 7 Mar 2013 13:23:28 -0800
x86: Do not try to sync identity map for non-mapped pages
kernel_map_sync_memtype() is called from a variety of contexts. The
pat.c code that calls it seems to ensure that it is not called for
non-ram areas by checking via pat_pagerange_is_ram(). It is important
that it only be called on the actual identity map because there *IS*
no map to sync for highmem pages, or for memory holes.
The ioremap.c uses are not as careful as those from pat.c, and call
kernel_map_sync_memtype() on PCI space which is in the middle of the
kernel identity map _range_, but is not actually mapped.
This patch adds a check to kernel_map_sync_memtype() which probably
duplicates some of the checks already in pat.c. But, it is necessary
for the ioremap.c uses and shouldn't hurt other callers.
I have reproduced this bug and this patch fixes it for me and the
original bug reporter:
https://lkml.org/lkml/2013/2/5/396
Signed-off-by: Dave Hansen <dave@linux.vnet.ibm.com>
Link: http://lkml.kernel.org/r/20130307163151.D9B58C4E@kernel.stglabs.ibm.com
Signed-off-by: Dave Hansen <dave@sr71.net>
Tested-by: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
---
arch/x86/mm/pat.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/arch/x86/mm/pat.c b/arch/x86/mm/pat.c
index 2610bd9..6574388 100644
--- a/arch/x86/mm/pat.c
+++ b/arch/x86/mm/pat.c
@@ -563,6 +563,13 @@ int kernel_map_sync_memtype(u64 base, unsigned long size, unsigned long flags)
if (base > __pa(high_memory-1))
return 0;
+ /*
+ * some areas in the middle of the kernel identity range
+ * are not mapped, like the PCI space.
+ */
+ if (!page_is_ram(base >> PAGE_SHIFT))
+ return 0;
+
id_sz = (__pa(high_memory-1) <= base + size) ?
__pa(high_memory) - base :
size;
next prev parent reply other threads:[~2013-03-07 22:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 16:31 [PATCH] do not try to sync identity map for non-mapped pages Dave Hansen
2013-03-07 21:59 ` tip-bot for Dave Hansen [this message]
2013-03-07 22:05 ` Tetsuo Handa
2013-03-07 22:13 ` H. Peter Anvin
2013-04-07 13:33 ` Borislav Petkov
2013-04-07 16:34 ` H. Peter Anvin
2013-04-07 17:25 ` Borislav Petkov
2013-04-08 20:33 ` Dave Hansen
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=tip-60f583d56aa515b896a9d94f860f52640c1e8a75@git.kernel.org \
--to=tipbot@zytor.com \
--cc=dave@linux.vnet.ibm.com \
--cc=dave@sr71.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=tglx@linutronix.de \
/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