summaryrefslogtreecommitdiffstats
path: root/arch
diff options
context:
space:
mode:
authorJan Beulich <JBeulich@suse.com>2011-09-15 08:52:40 +0100
committerKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>2011-09-15 04:39:46 -0400
commit61cca2fab7ecba18f9b9680cd736ef5fa82ad3b1 (patch)
tree9a7fe7390778f20bfadcd5ecb9679785b5380cf7 /arch
parent773659483685d652970583384a0294948e57f8b3 (diff)
downloadop-kernel-dev-61cca2fab7ecba18f9b9680cd736ef5fa82ad3b1.zip
op-kernel-dev-61cca2fab7ecba18f9b9680cd736ef5fa82ad3b1.tar.gz
xen/i386: follow-up to "replace order-based range checking of M2P table by linear one"
The numbers obtained from the hypervisor really can't ever lead to an overflow here, only the original calculation going through the order of the range could have. This avoids the (as Jeremy points outs) somewhat ugly NULL-based calculation here. Signed-off-by: Jan Beulich <jbeulich@novell.com> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Diffstat (limited to 'arch')
-rw-r--r--arch/x86/xen/mmu.c6
1 files changed, 2 insertions, 4 deletions
diff --git a/arch/x86/xen/mmu.c b/arch/x86/xen/mmu.c
index 24abc1f..a3872f7 100644
--- a/arch/x86/xen/mmu.c
+++ b/arch/x86/xen/mmu.c
@@ -1721,10 +1721,8 @@ void __init xen_setup_machphys_mapping(void)
machine_to_phys_nr = MACH2PHYS_NR_ENTRIES;
}
#ifdef CONFIG_X86_32
- if ((machine_to_phys_mapping + machine_to_phys_nr)
- < machine_to_phys_mapping)
- machine_to_phys_nr = (unsigned long *)NULL
- - machine_to_phys_mapping;
+ WARN_ON((machine_to_phys_mapping + (machine_to_phys_nr - 1))
+ < machine_to_phys_mapping);
#endif
}
OpenPOWER on IntegriCloud