[PATCH][GIT PULL][v2.6.39] tracing: Fix set_ftrace_filter probefunction display

From: Steven Rostedt
Date: Tue Mar 22 2011 - 21:32:53 EST


This patch was buried away in my INBOX, and I recently discovered it. I
tested out the scenario that Jiri posted and sure enough it is broken.
This patch does indeed fix the issue.

As the merge window is still open and this is a simple patch that fixes
a long standing bug, could you pull it for 2.6.39.


-- Steve

Please pull the latest tip/perf/urgent tree, which can be found at:


Jiri Olsa (1):
tracing: Fix set_ftrace_filter probe function display

kernel/trace/ftrace.c | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
commit 1106b6997df7d0c0487e21fd9c9dd2ce3d4a52db
Author: Jiri Olsa <jolsa@xxxxxxxxxx>
Date: Wed Feb 16 17:35:34 2011 +0100

tracing: Fix set_ftrace_filter probe function display

If one or more function probes (like traceon) are enabled,
and there's no other function filter, the first probe
func is skipped (which one depends on the position in the hash).

$ echo sys_open:traceon sys_close:traceon > ./set_ftrace_filter
$ cat set_ftrace_filter
#### all functions enabled ####

The reason was, that in the case of no other function filter,
the func_pos was not properly updated before calling t_hash_start.

Signed-off-by: Jiri Olsa <jolsa@xxxxxxxxxx>
LKML-Reference: <1297874134-7008-1-git-send-email-jolsa@xxxxxxxxxx>
Signed-off-by: Steven Rostedt <rostedt@xxxxxxxxxxx>

diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
index 888b611..c075f4e 100644
--- a/kernel/trace/ftrace.c
+++ b/kernel/trace/ftrace.c
@@ -1467,7 +1467,7 @@ t_next(struct seq_file *m, void *v, loff_t *pos)
return t_hash_next(m, pos);

- iter->pos = *pos;
+ iter->pos = iter->func_pos = *pos;

if (iter->flags & FTRACE_ITER_PRINTALL)
return t_hash_start(m, pos);
@@ -1502,7 +1502,6 @@ t_next(struct seq_file *m, void *v, loff_t *pos)
if (!rec)
return t_hash_start(m, pos);

- iter->func_pos = *pos;
iter->func = rec;

return iter;

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/