[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190508135921.83b451dca88c79a1ae8e4fd4@kernel.org>
Date: Wed, 8 May 2019 13:59:21 +0900
From: Masami Hiramatsu <mhiramat@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Andreas Ziegler <andreas.ziegler@....de>,
Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/3] tracing: probeevent: Fix probe argument parser
and handler
On Tue, 7 May 2019 22:10:06 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:
> On Tue, 7 May 2019 22:55:22 +0900
> Masami Hiramatsu <mhiramat@...nel.org> wrote:
>
> > 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.
> >
>
> Thanks Masami,
>
> I applied these to my queue.
Thank you, Steve! I'll rebase other series on that.
--
Masami Hiramatsu <mhiramat@...nel.org>
Powered by blists - more mailing lists