[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <342740659.2887.1549307721609.JavaMail.zimbra@efficios.com>
Date: Mon, 4 Feb 2019 14:15:21 -0500 (EST)
From: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
To: Kees Cook <keescook@...omium.org>
Cc: William Cohen <wcohen@...hat.com>, stable@...r.kernel.org,
Laura Abbott <labbott@...hat.com>,
Masami Hiramatsu <mhiramat@...nel.org>,
Russell King <rmk+kernel@...linux.org.uk>,
linux-kernel <linux-kernel@...r.kernel.org>,
lttng@...iableembeddedsystems.com,
lttng-dev <lttng-dev@...ts.lttng.org>
Subject: BUG: optimized kprobes illegal instructions in v4.19 stable kernels
Hi,
I notice this commit as a possible culprit of the illegal instructions my lttng
users are noticing on arm32 when using kprobes on a v4.19.13 Linux kernel
in a Yocto environment [1]. They were able to reproduce the issue with perf
as well.
commit e46daee53bb50bde38805f1823a182979724c229
Author: Kees Cook <keescook@...omium.org>
Date: Tue Oct 30 22:12:56 2018 +0100
ARM: 8806/1: kprobes: Fix false positive with FORTIFY_SOURCE
I *think* the intent there was to do
- memcpy(code, &optprobe_template_entry,
+ memcpy(code, (unsigned long *)&optprobe_template_entry,
But if you look at the commit, the "&" seems to have been stripped away,
which happens to change the behavior significantly.
Has this change ever been runtime-tested ?
It has been backported to:
- 4.19 stable as commit 3fe0c68aea21
- 4.14 stable as commit f9e0bc710347
Thanks,
Mathieu
[1] https://bugs.lttng.org/issues/1174
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
Powered by blists - more mailing lists