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>
This commit is contained in:
committed by
Martin Schwidefsky
parent
ac1256f826
commit
f4f0d32bfb
@ -30,7 +30,7 @@
|
|||||||
* The stack trace can start at any of the three stacks and can potentially
|
* 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.
|
* 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,
|
__dump_trace(dump_trace_func_t func, void *data, unsigned long sp,
|
||||||
unsigned long low, unsigned long high)
|
unsigned long low, unsigned long high)
|
||||||
{
|
{
|
||||||
|
Reference in New Issue
Block a user