[lkml]   [2019]   [Mar]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject[RFC PATCH v2 0/7] tracing: Use common error_log with probe events

Here is the 2nd version of using common error_log with probe events.
Previous version is here.

In this version, I've updated some error messages according to
Steve's comment, adjust some error position, and update testcase
to simplify a bit.

- [4/7]: Update error message according to Steve's comment (Thanks!)
- [6/7]: Update error message, adjust error positions, and add uprobe errors
- [7/7]: Specify error position in command string by "^".
Clear error_log right before writing command.
Add uprobe syntax error checker

Thank you,


Masami Hiramatsu (7):
tracing/probe: Check maxactive error cases
tracing/probe: Check event name length correctly
tracing/probe: Check the size of argument name and body
tracing/probe: Check event/group naming rule at parsing
tracing/probe: Verify alloc_trace_*probe() result
tracing: Use tracing error_log with probe events
selftests/ftrace: Add error_log testcase for probe errors

kernel/trace/trace_kprobe.c | 90 ++++--
kernel/trace/trace_probe.c | 282 +++++++++++++++-----
kernel/trace/trace_probe.h | 78 +++++-
kernel/trace/trace_uprobe.c | 52 ++--
.../ftrace/test.d/kprobe/ | 93 +++++++
.../ftrace/test.d/kprobe/ | 31 ++
6 files changed, 494 insertions(+), 132 deletions(-)
create mode 100644 tools/testing/selftests/ftrace/test.d/kprobe/
create mode 100644 tools/testing/selftests/ftrace/test.d/kprobe/

Masami Hiramatsu <>

 \ /
  Last update: 2019-03-14 05:30    [W:0.056 / U:6.132 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site