diff options
| author | Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com> | 2010-06-18 12:22:40 +0900 |
|---|---|---|
| committer | H. Peter Anvin <hpa@linux.intel.com> | 2010-07-09 11:42:03 -0700 |
| commit | ffa71f33a820d1ab3f2fc5723819ac60fb76080b (patch) | |
| tree | fb7fb08c43a773f771a49ac765e9330e07d32eef /mm/vmalloc.c | |
| parent | d7a0380dc3e6607d30ccdfc3cfc2ccee0d966716 (diff) | |
| download | linux-stable-ffa71f33a820d1ab3f2fc5723819ac60fb76080b.tar.gz linux-stable-ffa71f33a820d1ab3f2fc5723819ac60fb76080b.tar.bz2 linux-stable-ffa71f33a820d1ab3f2fc5723819ac60fb76080b.zip | |
x86, ioremap: Fix incorrect physical address handling in PAE mode
Current x86 ioremap() doesn't handle physical address higher than
32-bit properly in X86_32 PAE mode. When physical address higher than
32-bit is passed to ioremap(), higher 32-bits in physical address is
cleared wrongly. Due to this bug, ioremap() can map wrong address to
linear address space.
In my case, 64-bit MMIO region was assigned to a PCI device (ioat
device) on my system. Because of the ioremap()'s bug, wrong physical
address (instead of MMIO region) was mapped to linear address space.
Because of this, loading ioatdma driver caused unexpected behavior
(kernel panic, kernel hangup, ...).
Signed-off-by: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
LKML-Reference: <4C1AE680.7090408@jp.fujitsu.com>
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Diffstat (limited to 'mm/vmalloc.c')
| -rw-r--r-- | mm/vmalloc.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/mm/vmalloc.c b/mm/vmalloc.c index ae007462b7f6..b7e314b1009f 100644 --- a/mm/vmalloc.c +++ b/mm/vmalloc.c @@ -2403,7 +2403,7 @@ static int s_show(struct seq_file *m, void *p) seq_printf(m, " pages=%d", v->nr_pages); if (v->phys_addr) - seq_printf(m, " phys=%lx", v->phys_addr); + seq_printf(m, " phys=%llx", (unsigned long long)v->phys_addr); if (v->flags & VM_IOREMAP) seq_printf(m, " ioremap"); |