summaryrefslogtreecommitdiff
path: root/arch/s390/mm/vmem.c
diff options
context:
space:
mode:
authorAlexander Gordeev <agordeev@linux.ibm.com>2023-07-04 08:46:26 +0300
committerAlexander Gordeev <agordeev@linux.ibm.com>2023-07-04 08:46:26 +0300
commit54372cf043276735e29045abf998895b2ac277cf (patch)
treeeed37120a84e3b2f45b89a2a51b264716ff35d16 /arch/s390/mm/vmem.c
parent6aca56c024e42577c28706a85979a6967b9b5e97 (diff)
downloadlinux-54372cf043276735e29045abf998895b2ac277cf.tar.xz
Revert "s390/mm: get rid of VMEM_MAX_PHYS macro"
This reverts commit 456be42aa713e7f83b467db66ceae779431c7d9d. The assumption VMEM_MAX_PHYS should match ident_map_size is wrong. At least discontiguous saved segments (DCSS) could be loaded at addresses beyond ident_map_size and dcssblk device driver might fail as result. Reported-by: Gerald Schaefer <gerald.schaefer@linux.ibm.com> Signed-off-by: Alexander Gordeev <agordeev@linux.ibm.com>
Diffstat (limited to 'arch/s390/mm/vmem.c')
-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 9db048ccfcc8..b26649233d12 100644
--- a/arch/s390/mm/vmem.c
+++ b/arch/s390/mm/vmem.c
@@ -531,7 +531,7 @@ struct range arch_get_mappable_range(void)
struct range mhp_range;
mhp_range.start = 0;
- mhp_range.end = ident_map_size - 1;
+ mhp_range.end = VMEM_MAX_PHYS - 1;
return mhp_range;
}