Re: [PATCH 1/2] x86/unwind/orc: Disable KASAN checking in the ORC unwinder, part 2

2021-02-05 Thread Steven Rostedt
On Fri, 5 Feb 2021 08:24:02 -0600 Josh Poimboeuf wrote: > KASAN reserves "redzone" areas between stack frames in order to detect > stack overruns. A read or write to such an area triggers a KASAN > "stack-out-of-bounds" BUG. > > Normally, the ORC unwinder stays in-bounds and doesn't access the

Re: [PATCH 1/2] x86/unwind/orc: Disable KASAN checking in the ORC unwinder, part 2

2021-02-05 Thread Ivan Babrou
On Fri, Feb 5, 2021 at 6:24 AM Josh Poimboeuf wrote: > > KASAN reserves "redzone" areas between stack frames in order to detect > stack overruns. A read or write to such an area triggers a KASAN > "stack-out-of-bounds" BUG. > > Normally, the ORC unwinder stays in-bounds and doesn't access the > r

[PATCH 1/2] x86/unwind/orc: Disable KASAN checking in the ORC unwinder, part 2

2021-02-05 Thread Josh Poimboeuf
KASAN reserves "redzone" areas between stack frames in order to detect stack overruns. A read or write to such an area triggers a KASAN "stack-out-of-bounds" BUG. Normally, the ORC unwinder stays in-bounds and doesn't access the redzone. But sometimes it can't find ORC metadata for a given instr