aboutsummaryrefslogtreecommitdiffstats
path: root/ipc/msgutil.c
diff options
context:
space:
mode:
authorDave Hansen <dave@sr71.net>2013-03-07 08:31:51 -0800
committerH. Peter Anvin <hpa@zytor.com>2013-03-07 13:23:28 -0800
commit60f583d56aa515b896a9d94f860f52640c1e8a75 (patch)
treeb3e140c991bbdfe01eaa029d452784ef5242feb8 /ipc/msgutil.c
parentx86, doc: Be explicit about what the x86 struct boot_params requires (diff)
downloadlinux-dev-60f583d56aa515b896a9d94f860f52640c1e8a75.tar.xz
linux-dev-60f583d56aa515b896a9d94f860f52640c1e8a75.zip
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>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions