s390/kasan: sort out physical vs virtual memory confusion
authorAlexander Gordeev <agordeev@linux.ibm.com>
Tue, 13 Dec 2022 10:31:39 +0000 (11:31 +0100)
committerHeiko Carstens <hca@linux.ibm.com>
Fri, 13 Jan 2023 13:15:04 +0000 (14:15 +0100)
commitaae2f753d2a96fb062c3cb710ccbd4cb3d5b9452
tree535aaf72a9f98054418f77647ba45c8b50cfeeb7
parent639886b71ddef085a0e7bb1f225b8ae3eda5c06f
s390/kasan: sort out physical vs virtual memory confusion

The kasan early boot memory allocators operate on pgalloc_pos
and segment_pos physical address pointers, but fail to convert
it to the corresponding virtual pointers.

Currently it is not a problem, since virtual and physical
addresses on s390 are the same. Nevertheless, should they
ever differ, this would cause an invalid pointer access.

Reviewed-by: Heiko Carstens <hca@linux.ibm.com>
Signed-off-by: Alexander Gordeev <agordeev@linux.ibm.com>
Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
arch/s390/mm/kasan_init.c