kmsan: accept ranges starting with 0 on s390
On s390 the virtual address 0 is valid (current CPU's lowcore is mapped there), therefore KMSAN should not complain about it. Disable the respective check on s390. There doesn't seem to be a Kconfig option to describe this situation, so explicitly check for s390. Link: https://lkml.kernel.org/r/20240621113706.315500-22-iii@linux.ibm.com Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com> Reviewed-by: Alexander Potapenko <glider@google.com> Cc: Alexander Gordeev <agordeev@linux.ibm.com> Cc: Christian Borntraeger <borntraeger@linux.ibm.com> Cc: Christoph Lameter <cl@linux.com> Cc: David Rientjes <rientjes@google.com> Cc: Dmitry Vyukov <dvyukov@google.com> Cc: Heiko Carstens <hca@linux.ibm.com> Cc: Hyeonggon Yoo <42.hyeyoo@gmail.com> Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com> Cc: <kasan-dev@googlegroups.com> Cc: Marco Elver <elver@google.com> Cc: Mark Rutland <mark.rutland@arm.com> Cc: Masami Hiramatsu (Google) <mhiramat@kernel.org> Cc: Pekka Enberg <penberg@kernel.org> Cc: Roman Gushchin <roman.gushchin@linux.dev> Cc: Steven Rostedt (Google) <rostedt@goodmis.org> Cc: Sven Schnelle <svens@linux.ibm.com> Cc: Vasily Gorbik <gor@linux.ibm.com> Cc: Vlastimil Babka <vbabka@suse.cz> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
This commit is contained in:
parent
89f42df66c
commit
cd613bd699
@ -33,7 +33,10 @@ static void __init kmsan_record_future_shadow_range(void *start, void *end)
|
||||
bool merged = false;
|
||||
|
||||
KMSAN_WARN_ON(future_index == NUM_FUTURE_RANGES);
|
||||
KMSAN_WARN_ON((nstart >= nend) || !nstart || !nend);
|
||||
KMSAN_WARN_ON((nstart >= nend) ||
|
||||
/* Virtual address 0 is valid on s390. */
|
||||
(!IS_ENABLED(CONFIG_S390) && !nstart) ||
|
||||
!nend);
|
||||
nstart = ALIGN_DOWN(nstart, PAGE_SIZE);
|
||||
nend = ALIGN(nend, PAGE_SIZE);
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user