Revision bbd1d27d863d5c0acee65ecd0c2e34035e1df5ea authored by Steven Rostedt (VMware) on 11 July 2017, 23:21:04 UTC, committed by Steven Rostedt (VMware) on 11 July 2017, 23:21:04 UTC
The "stack_trace_filter" file only makes sense if DYNAMIC_FTRACE is configured in. If it is not, then the user can not filter any functions. Not only that, the open function causes warnings when DYNAMIC_FTRACE is not set. Link: http://lkml.kernel.org/r/20170710110521.600806-1-arnd@arndb.de Reported-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
1 parent dc8d387
| File | Mode | Size |
|---|---|---|
| api | ||
| bpf | ||
| lockdep | ||
| subcmd | ||
| symbol | ||
| traceevent | ||
| bitmap.c | -rw-r--r-- | 1.7 KB |
| find_bit.c | -rw-r--r-- | 2.6 KB |
| hweight.c | -rw-r--r-- | 1.7 KB |
| rbtree.c | -rw-r--r-- | 14.7 KB |
| str_error_r.c | -rw-r--r-- | 1000 bytes |
| string.c | -rw-r--r-- | 2.1 KB |
| vsprintf.c | -rw-r--r-- | 539 bytes |
Computing file changes ...
