public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Andreas Ziegler <andreas.ziegler@fau.de>,
	Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] tracing: probeevent: Fix probe argument parser and handler
Date: Thu, 17 Jan 2019 09:23:02 -0500	[thread overview]
Message-ID: <20190117092302.596b4538@vmware.local.home> (raw)
In-Reply-To: <154773287750.2285.5509629487576876823.stgit@devbox>

On Thu, 17 Jan 2019 22:47:58 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:

> Hi,
> 
> This series fixes several bugs in probe event argument parser
> and handler routines.

Hi Masami,

Can you resend with a "Fixes:" tag to each of the patches, so that it
is easy to see what patch needs to be backported to which stable kernel
(or not any stable release if the patch fixes something in 5.0-rc).

Thanks!

-- Steve

> 
> Recently 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_tmpl.h |    2 +-
>  kernel/trace/trace_uprobe.c     |   15 +++++++++++++--
>  3 files changed, 21 insertions(+), 9 deletions(-)
> 
> --
> Masami Hiramatsu (Linaro) <mhiramat@kernel.org>


  parent reply	other threads:[~2019-01-17 14:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17 13:47 [PATCH 0/3] tracing: probeevent: Fix probe argument parser and handler Masami Hiramatsu
2019-01-17 13:48 ` [PATCH 1/3] tracing: uprobes: Re-enable $comm support for uprobe events Masami Hiramatsu
2019-01-17 13:48 ` [PATCH 2/3] tracing: probeevent: Do not accumulate on ret variable Masami Hiramatsu
2019-01-17 13:49 ` [PATCH 3/3] tracing: probeevent: Fix to make the type of $comm string Masami Hiramatsu
2019-01-17 14:23 ` Steven Rostedt [this message]
2019-01-17 23:30   ` [PATCH 0/3] tracing: probeevent: Fix probe argument parser and handler Masami Hiramatsu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190117092302.596b4538@vmware.local.home \
    --to=rostedt@goodmis.org \
    --cc=andreas.ziegler@fau.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox