aboutsummaryrefslogtreecommitdiffstats
path: root/tools
diff options
context:
space:
mode:
authorSteven Rostedt <srostedt@redhat.com>2010-09-14 11:21:11 -0400
committerSteven Rostedt <rostedt@goodmis.org>2010-09-14 15:14:20 -0400
commit57c072c7113f54f9512624d6c665db6184448782 (patch)
treec005a9325d308763bd1763853395c7b13010b5e3 /tools
parenttracing: Keep track of set_ftrace_filter position and allow lseek again (diff)
downloadlinux-dev-57c072c7113f54f9512624d6c665db6184448782.tar.xz
linux-dev-57c072c7113f54f9512624d6c665db6184448782.zip
tracing: Fix reading of set_ftrace_filter across lists
If we do: # cd /sys/kernel/debug # echo 'do_IRQ:traceon schedule:traceon sys_write:traceon' > \ set_ftrace_filter # cat set_ftrace_filter We get the following output: #### all functions enabled #### sys_write:traceon:unlimited schedule:traceon:unlimited do_IRQ:traceon:unlimited This outputs two lists. One is the fact that all functions are currently enabled for function tracing, the other has three probed functions, which happen to have 'traceon' as their commands. Currently, when reading the first list (functions enabled) the seq_file code will receive a "NULL" from the t_next() function causing it to exit early. This makes "read()" from userspace stop reading the code at this boarder. Although read is allowed to do this, some (broken) applications might consider this an end of file and stop early. This patch adds the start of the second list to t_next() when it finishes the first list. It is a simple change and gives the set_ftrace_filter file nicer reading ability. Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions