Re: [PATCH v4] kprobes: unpoison stack in jprobe_return() for KASAN

2016-10-14 Thread Dmitry Vyukov
On Fri, Oct 14, 2016 at 3:08 PM, Mark Rutland wrote: > On Fri, Oct 14, 2016 at 01:54:30PM +0200, Dmitry Vyukov wrote: >> KASAN stack instrumentation poisons stack redzones on function entry >> and unpoisons them on function exit. If a function exits abnormally >> (e.g. with a longjmp like jprobe_r

Re: [PATCH v4] kprobes: unpoison stack in jprobe_return() for KASAN

2016-10-14 Thread Mark Rutland
On Fri, Oct 14, 2016 at 01:54:30PM +0200, Dmitry Vyukov wrote: > KASAN stack instrumentation poisons stack redzones on function entry > and unpoisons them on function exit. If a function exits abnormally > (e.g. with a longjmp like jprobe_return()), stack redzones are left > poisoned. Later this le

[PATCH v4] kprobes: unpoison stack in jprobe_return() for KASAN

2016-10-14 Thread Dmitry Vyukov
KASAN stack instrumentation poisons stack redzones on function entry and unpoisons them on function exit. If a function exits abnormally (e.g. with a longjmp like jprobe_return()), stack redzones are left poisoned. Later this leads to random KASAN false reports. Unpoison stack redzones in the fram