Update s390x_vr_IS_VMALLOC_ADDR() to include a non-zero vmalloc_start
check, making it consistent with s390x_generic_IS_VMALLOC_ADDR().

Fixes: d0164e7e480a ("s390x: uncouple physical and virtual memory spaces")
Signed-off-by: Mikhail Zaslonko <[email protected]>
---
 s390x.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/s390x.c b/s390x.c
index 0e8e2b3..1117bf0 100644
--- a/s390x.c
+++ b/s390x.c
@@ -724,13 +724,13 @@ static ulong s390x_vr_PTOV(ulong paddr)
 {
        return paddr + machdep->identity_map_base;
 }
 
 static int s390x_vr_IS_VMALLOC_ADDR(ulong vaddr)
 {
-       return (vaddr >= vt->vmalloc_start && vaddr < machdep->kvbase);
+       return (vt->vmalloc_start && vaddr >= vt->vmalloc_start && vaddr < 
machdep->kvbase);
 }
 
 ulong s390x_VTOP(ulong vaddr)
 {
        return machdep->machspec->virt_to_phys(vaddr);
 }
-- 
2.49.0
--
Crash-utility mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://${domain_name}/admin/lists/devel.lists.crash-utility.osci.io/
Contribution Guidelines: https://github.com/crash-utility/crash/wiki

Reply via email to