[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 15 Oct 2016 08:30:43 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Dmitry Vyukov <dvyukov@...gle.com>
Cc: rostedt@...dmis.org, mingo@...hat.com, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, ryabinin.a.a@...il.com,
surovegin@...gle.com, Mark Rutland <mark.rutland@....com>,
Catalin Marinas <catalin.marinas@....com>,
Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
Alexander Potapenko <glider@...gle.com>,
Will Deacon <will.deacon@....com>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Ananth N Mavinakayanahalli <ananth@...ux.vnet.ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@...el.com>,
"David S. Miller" <davem@...emloft.net>,
Masami Hiramatsu <mhiramat@...nel.org>, x86@...nel.org,
kasan-dev@...glegroups.com
Subject: Re: [PATCH v5] kprobes: unpoison stack in jprobe_return() for KASAN
* Dmitry Vyukov <dvyukov@...gle.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
Powered by blists - more mailing lists