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

2016-10-16 Thread Ingo Molnar
* Dmitry Vyukov wrote: > On Sat, Oct 15, 2016 at 8:30 AM, Ingo Molnar wrote: > > > > * Dmitry Vyukov wrote: > > > >> KASAN stack instrumentation poisons stack redzones on function entry > >> and unpoisons them on function exit. If a

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

2016-10-16 Thread Ingo Molnar
* Dmitry Vyukov wrote: > On Sat, Oct 15, 2016 at 8:30 AM, Ingo Molnar wrote: > > > > * 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

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

2016-10-15 Thread Dmitry Vyukov
On Sat, Oct 15, 2016 at 8:30 AM, Ingo Molnar wrote: > > * 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

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

2016-10-15 Thread Dmitry Vyukov
On Sat, Oct 15, 2016 at 8:30 AM, Ingo Molnar wrote: > > * 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

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

2016-10-15 Thread Ingo Molnar
* 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 leads to random

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

2016-10-15 Thread Ingo Molnar
* 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 leads to random KASAN false reports. >

[PATCH v5] 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

[PATCH v5] 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