[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <155723732200.9149.10482668315693777743.stgit@devnote2>
Date: Tue, 7 May 2019 22:55:22 +0900
From: Masami Hiramatsu <mhiramat@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Andreas Ziegler <andreas.ziegler@....de>,
Masami Hiramatsu <mhiramat@...nel.org>,
Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org
Subject: [PATCH v3 0/3] tracing: probeevent: Fix probe argument parser and handler
Hi,
Here is the 3rd version of series to fix several bugs in probe event
argument parser and handler routines.
In this version I updated patch [1/3] according to Steve's comment.
I got 2 issues reported by Andreas, see
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1899098.html
One issue is already fixed by Andreas (Thanks!) but $comm handling
issue still exists on uprobe event. [1/3] fixes it.
And I found other issues around that, [2/3] is just a trivial cleanup,
[3/3] fixes $comm type issue which occurs not only uprobe events but
also on kprobe events. Anyway, after this series applied, $comm must
be "string" type and not be an array.
Thank you,
---
Masami Hiramatsu (3):
tracing: uprobes: Re-enable $comm support for uprobe events
tracing: probeevent: Do not accumulate on ret variable
tracing: probeevent: Fix to make the type of $comm string
kernel/trace/trace_probe.c | 13 +++++++------
kernel/trace/trace_probe.h | 1 +
kernel/trace/trace_probe_tmpl.h | 2 +-
kernel/trace/trace_uprobe.c | 13 +++++++++++--
4 files changed, 20 insertions(+), 9 deletions(-)
--
Masami Hiramatsu <mhiramat@...nel.org>
Powered by blists - more mailing lists