From: Vasily Gorbik <gor@linux.ibm.com>
Date: Mon, 20 Nov 2017 11:17:19 +0000 (+0100)
Subject: s390/dumpstack: disable __dump_trace kasan instrumentation
X-Git-Tag: v5.15~7800^2~28
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=f4f0d32bfb273537fcea9febc7081dac0252dcc0;p=platform%2Fkernel%2Flinux-starfive.git

s390/dumpstack: disable __dump_trace kasan instrumentation

Walking async_stack produces false positives. Disable __dump_trace
function instrumentation for now.

Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
---

diff --git a/arch/s390/kernel/dumpstack.c b/arch/s390/kernel/dumpstack.c
index ef85a00..d4c88e1 100644
--- a/arch/s390/kernel/dumpstack.c
+++ b/arch/s390/kernel/dumpstack.c
@@ -30,7 +30,7 @@
  * The stack trace can start at any of the three stacks and can potentially
  * touch all of them. The order is: panic stack, async stack, sync stack.
  */
-static unsigned long
+static unsigned long __no_sanitize_address
 __dump_trace(dump_trace_func_t func, void *data, unsigned long sp,
 	     unsigned long low, unsigned long high)
 {