tracing: seqfile fixes
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 7 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | tracing/events: don't increment @pos in s_start()kernel/ | +22 | 0 replies | |
| 2/5 | tracing_bprintk: don't increment @pos in t_start()kernel/ | +6 | 4 replies | |
| 3/5 | trace_stat: don't increment @pos in stat_seq_start()kernel/ | +1 | 0 replies | |
| 4/5 | ftrace: don't increment @pos in g_start()kernel/ | +13 | 6 replies | |
| 5/5 | tracing: reset iterator in t_start()kernel/ | +4 | 3 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/5] tracing: seqfile fixes
While testing syscall tracepoints proposed by Jason, I found some entries were missing when reading available_events.
It turned out there's bug in seqfile handling. The bug is, it's wrong to increment @pos in seq start().
I fixed similar bugs in some other places. (the last patch fixes a different seqfile bug)
[PATCH 1/5] tracing/events: don't increment @pos in s_start() [PATCH 2/5] tracing_bprintk: don't increment @pos in t_start() [PATCH 3/5] trace_stat: don't increment @pos in stat_seq_start() [PATCH 4/5] ftrace: don't increment @pos in g_start() [PATCH 5/5] tracing: reset iterator in t_start()
--- kernel/trace/ftrace.c | 28 +++++++++++++--------------- kernel/trace/trace.c | 18 ++++-------------- kernel/trace/trace_events.c | 28 ++++++++++++++++++++++------ kernel/trace/trace_printk.c | 26 ++++++-------------------- kernel/trace/trace_stat.c | 6 +----- 5 files changed, 46 insertions(+), 60 deletions(-)