Linus,
There's been a few memory issues found with ftrace.
One was simply a memory leak where not all was being freed that should
have been in releasing a file pointer on set_graph_function.
Then Thomas found that the ftrace trampolines were marked for read/write
as well as execute. To shrink the possible attack surface, he added
calls to set them to ro. Which also uncovered some other issues with
freeing module allocated memory that had its permissions changed.
Kprobes had a similar issue which is fixed and a selftest was added
to trigger that issue again.
Please pull the latest trace-v4.12-rc2 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
trace-v4.12-rc2
Tag SHA1: 61ffee417e15b119c84e95b07348fdffd916f254
Head SHA1: 6ee98ffeea0bc9e072e419497d78697d8afcdd6d
Luis Henriques (1):
ftrace: Fix memory leak in ftrace_graph_release()
Masami Hiramatsu (2):
kprobes/x86: Fix to set RWX bits correctly before releasing trampoline
selftests/ftrace: Add a testcase for many kprobe events
Steven Rostedt (VMware) (1):
x86/mm/ftrace: Do not bug in early boot on irqs_disabled in
cpu_flush_range()
Thomas Gleixner (1):
x86/ftrace: Make sure that ftrace trampolines are not RWX
----
arch/x86/kernel/ftrace.c | 20 ++++++++++++++------
arch/x86/kernel/kprobes/core.c | 9 +++++++++
arch/x86/mm/pageattr.c | 2 +-
kernel/kprobes.c | 2 +-
kernel/trace/ftrace.c | 2 +-
.../ftrace/test.d/kprobe/multiple_kprobes.tc | 21 +++++++++++++++++++++
6 files changed, 47 insertions(+), 9 deletions(-)
create mode 100644
tools/testing/selftests/ftrace/test.d/kprobe/multiple_kprobes.tc
