diff options
| author | Daniel Axtens <dja@axtens.net> | 2021-06-14 22:09:07 +1000 |
|---|---|---|
| committer | Michael Ellerman <mpe@ellerman.id.au> | 2021-06-17 00:09:11 +1000 |
| commit | b112fb913b5b5705db22efa90ec60f42518934af (patch) | |
| tree | 78ce3f3f8d13289e02ee7fc9782ae210abb361c0 /arch/powerpc/kernel/stacktrace.c?id=b112fb913b5b5705db22efa90ec60f42518934af | |
| parent | d81090ed44c0d15abf2b07663d5f0b9e5ba51525 (diff) | |
powerpc: make stack walking KASAN-safe
Make our stack-walking code KASAN-safe by using __no_sanitize_address.
Generic code, arm64, s390 and x86 all make accesses unchecked for similar
sorts of reasons: when unwinding a stack, we might touch memory that KASAN
has marked as being out-of-bounds. In ppc64 KASAN development, I hit this
sometimes when checking for an exception frame - because we're checking
an arbitrary offset into the stack frame.
See commit 20955746320e ("s390/kasan: avoid false positives during stack
unwind"), commit bcaf669b4bdb ("arm64: disable kasan when accessing
frame->fp in unwind_frame"), commit 91e08ab0c851 ("x86/dumpstack:
Prevent KASAN false positive warnings") and commit 6e22c8366416
("tracing, kasan: Silence Kasan warning in check_stack of stack_tracer").
Signed-off-by: Daniel Axtens <dja@axtens.net>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/20210614120907.1952321-1-dja@axtens.net
Diffstat (limited to 'arch/powerpc/kernel/stacktrace.c?id=b112fb913b5b5705db22efa90ec60f42518934af')
0 files changed, 0 insertions, 0 deletions