| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <1401815569-10513-1-git-send-email-stfomichev@yandex-team.ru> Date: Tue, 3 Jun 2014 21:12:49 +0400 From: Stanislav Fomichev <stfomichev@...dex-team.ru> To: rostedt@...dmis.org, fweisbec@...il.com, mingo@...hat.com, jovi.zhangwei@...wei.com, namhyung.kim@....com, tom.zanussi@...ux.intel.com, stfomichev@...dex-team.ru Cc: linux-kernel@...r.kernel.org Subject: [PATCH] tracing: let user specify tracing_thresh after selecting function_graph Currently, tracing_thresh works only if we specify it before selecting function_graph tracer. If we do the opposite, tracing_thresh will change it's value, but it will not be applied. To fix it, we need to always register handlers which take tracing_thresh into account. Signed-off-by: Stanislav Fomichev <stfomichev@...dex-team.ru> --- kernel/trace/trace_functions_graph.c | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/kernel/trace/trace_functions_graph.c b/kernel/trace/trace_functions_graph.c index deff11200261..a894031986a3 100644 --- a/kernel/trace/trace_functions_graph.c +++ b/kernel/trace/trace_functions_graph.c @@ -433,12 +433,8 @@ static int graph_trace_init(struct trace_array *tr) int ret; set_graph_array(tr); - if (tracing_thresh) - ret = register_ftrace_graph(&trace_graph_thresh_return, - &trace_graph_thresh_entry); - else - ret = register_ftrace_graph(&trace_graph_return, - &trace_graph_entry); + ret = register_ftrace_graph(&trace_graph_thresh_return, + &trace_graph_thresh_entry); if (ret) return ret; tracing_start_cmdline_record(); -- 1.8.3.2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists