Patch "ftrace: Fix function pid filter on instances" has been added to the 4.10-stable tree
Subsystems (3)
This is a note to let you know that I've just added the patch titled
ftrace: Fix function pid filter on instances
to the 4.10-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
ftrace-fix-function-pid-filter-on-instances.patch
and it can be found in the queue-4.10 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
Quoted 1 line
From
d879d0b8c183aabeb9a65eba91f3f9e3c7e7b905Mon Sep 17 00:00:00 2001
From: Namhyung Kim <[email protected]>
Date: Mon, 17 Apr 2017 11:44:27 +0900
Subject: ftrace: Fix function pid filter on instances
From: Namhyung Kim <[email protected]>
commit d879d0b8c183aabeb9a65eba91f3f9e3c7e7b905 upstream.
When function tracer has a pid filter, it adds a probe to sched_switch to track if current task can be ignored. The probe checks the ftrace_ignore_pid from current tr to filter tasks. But it misses to delete the probe when removing an instance so that it can cause a crash due to the invalid tr pointer (use-after-free).
This is easily reproducible with the following:
# cd /sys/kernel/debug/tracing # mkdir instances/buggy # echo $$ > instances/buggy/set_ftrace_pid # rmdir instances/buggy
============================================================================
BUG: KASAN: use-after-free in ftrace_filter_pid_sched_switch_probe+0x3d/0x90 Read of size 8 by task kworker/0:1/17 CPU: 0 PID: 17 Comm: kworker/0:1 Tainted: G B 4.11.0-rc3 #198 Call Trace: dump_stack+0x68/0x9f kasan_object_err+0x21/0x70 kasan_report.part.1+0x22b/0x500 ? ftrace_filter_pid_sched_switch_probe+0x3d/0x90 kasan_report+0x25/0x30 __asan_load8+0x5e/0x70 ftrace_filter_pid_sched_switch_probe+0x3d/0x90 ? fpid_start+0x130/0x130 __schedule+0x571/0xce0 ...
To fix it, use ftrace_clear_pids() to unregister the probe. As instance_rmdir() already updated ftrace codes, it can just free the filter safely.
--- kernel/trace/ftrace.c | 9 +++++++++ kernel/trace/trace.c | 1 + kernel/trace/trace.h | 2 ++ 3 files changed, 12 insertions(+)
kernel/trace/ftrace.c +9 -0
@@ -5422,6 +5422,15 @@ static void clear_ftrace_pids(struct tratrace_free_pid_list (pid_list); } +void ftrace_clear_pids (struct trace_array *tr) +{ +mutex_lock (&ftrace_lock); + +clear_ftrace_pids (tr); + +mutex_unlock (&ftrace_lock); +} +static void ftrace_pid_reset (struct trace_array *tr) {mutex_lock (&ftrace_lock);
kernel/trace/trace.c +1 -0
@@ -7409,6 +7409,7 @@ static int instance_rmdir(const char *natracing_set_nop (tr);event_trace_del_tracer (tr); +ftrace_clear_pids (tr);ftrace_destroy_function_files (tr);tracefs_remove_recursive (tr->dir);free_trace_buffers (tr);
kernel/trace/trace.h +2 -0
@@ -884,6 +884,7 @@ int using_ftrace_ops_list_func(void);void ftrace_init_tracefs (struct trace_array *tr,struct dentry *d_tracer);void ftrace_init_tracefs_toplevel (struct trace_array *tr,struct dentry *d_tracer); +void ftrace_clear_pids (struct trace_array *tr);#else static inline int ftrace_trace_task (struct trace_array *tr) {
@@ -902,6 +903,7 @@ ftrace_init_global_array_ops(struct tracstatic inline void ftrace_reset_array_ops (struct trace_array *tr) { }static inline void ftrace_init_tracefs (struct trace_array *tr,struct dentry *d) { }static inline void ftrace_init_tracefs_toplevel (struct trace_array *tr,struct dentry *d) { } +static inline void ftrace_clear_pids (struct trace_array *tr) { }/* ftace_func_t type is not defined, use macro instead of static inline */ #define ftrace_init_array_ops (tr, func) do { } while (0)#endif /* CONFIG_FUNCTION_TRACER */
Patches currently in stable-queue which might be from [email protected] are
queue-4.10/ftrace-fix-function-pid-filter-on-instances.patch