summaryrefslogtreecommitdiffstats
path: root/arch
diff options
context:
space:
mode:
authorHeiko Carstens <heiko.carstens@de.ibm.com>2008-06-10 10:03:20 +0200
committerMartin Schwidefsky <schwidefsky@de.ibm.com>2008-06-10 10:03:27 +0200
commitee0ddadd086e25503f81be551c43f66472300acd (patch)
tree0f1606c133835abd3952af30efcee03230182139 /arch
parent12829126aa47758608578cc5be3a5adffc3d4b09 (diff)
downloadop-kernel-dev-ee0ddadd086e25503f81be551c43f66472300acd.zip
op-kernel-dev-ee0ddadd086e25503f81be551c43f66472300acd.tar.gz
[S390] vmemmap: fix off-by-one bug.
If a memory range is supposed to be added to the 1:1 mapping and it ends just below the maximum supported physical address it won't succeed. This is because a test doesn't consider that the end address is 1 smaller than start + size. Fix the comparison. Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com> Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'arch')
-rw-r--r--arch/s390/mm/vmem.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/s390/mm/vmem.c b/arch/s390/mm/vmem.c
index f591188..e4868bf 100644
--- a/arch/s390/mm/vmem.c
+++ b/arch/s390/mm/vmem.c
@@ -236,7 +236,7 @@ static int insert_memory_segment(struct memory_segment *seg)
{
struct memory_segment *tmp;
- if (seg->start + seg->size >= VMEM_MAX_PHYS ||
+ if (seg->start + seg->size > VMEM_MAX_PHYS ||
seg->start + seg->size < seg->start)
return -ERANGE;
OpenPOWER on IntegriCloud