Messages in this thread |  | | Date | Sat, 15 Oct 2016 08:30:43 +0200 | From | Ingo Molnar <> | Subject | Re: [PATCH v5] kprobes: unpoison stack in jprobe_return() for KASAN |
| |
* Dmitry Vyukov <dvyukov@google.com> 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. > > Unpoison stack redzones in the frames we are going to jump over > before doing actual longjmp in jprobe_return().
Does this affect any other architecture besides arm64? If not then it might make the most sense to merge this via the arm64 tree.
Thanks,
Ingo
|  |