public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Dean Nelson <dnelson@redhat.com>
Cc: a.p.zijlstra@chello.org, mingo@redhat.com, acme@kernel.org,
	namhyung@kernel.org, linux-kernel@vger.kernel.org,
	jolsa@kernel.org
Subject: Re: [PATCH v3] tools lib traceevent: add checks for returned EVENT_ERROR type
Date: Thu, 20 Aug 2015 13:05:58 -0400	[thread overview]
Message-ID: <20150820130558.4f3a2e35@grimm.local.home> (raw)
In-Reply-To: <20150820151632.13927.13791.email-sent-by-dnelson@teal>

On Thu, 20 Aug 2015 11:16:32 -0400
Dean Nelson <dnelson@redhat.com> wrote:

> Running the following perf-stat command on an arm64 system produces the
> following result...
> 
>   [root@aarch64 ~]# perf stat -e kmem:mm_page_alloc -a sleep 1
>     Warning: [kmem:mm_page_alloc] function sizeof not defined
>     Warning: Error: expected type 4 but read 0
>   Segmentation fault
>   [root@aarch64 ~]#
> 
> The second warning message and SIGSEGV stem from the issue expressed in the
> first warning message, and are the result of ignoring the EVENT_ERROR type
> returned back through the call chain.
> 
> Dealing with the first warning message is beyond the scope of this patch. But
> the second warning is addressed by this patch's first hunk. And the SIGSEGV is
> eliminated by its second hunk.

Patch looks fine, but this change log is lacking. I don't think you
need to resend though. But Arnaldo, can you add more to this change log
to describe the following, and that's only if I got it right ;-) If I
didn't get it right, then the change log definitely needs to be
explained better.

====
The second warning was a result of the first warning not stopping
processing after it detected the issue. That is, code that found the
issue reported the first problem, but because it did not exit out of
the functions smoothly, it caused the other warning to appear and not
only that, it later caused the SIGSEGV.
====

-- Steve

Other than that...

Acked-by: Steven Rostedt <rostedt@goodmis.org.



> 
> Signed-off-by: Dean Nelson <dnelson@redhat.com>

  parent reply	other threads:[~2015-08-20 17:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 15:16 [PATCH v3] tools lib traceevent: add checks for returned EVENT_ERROR type Dean Nelson
2015-08-20 15:57 ` Namhyung Kim
2015-08-20 17:05 ` Steven Rostedt [this message]
2015-08-20 17:56   ` Dean Nelson
2015-08-20 19:05     ` Arnaldo Carvalho de Melo
2015-08-20 20:43       ` Steven Rostedt
2015-08-21 13:34 ` Arnaldo Carvalho dn Melo
2015-08-21 14:03   ` Jiri Olsa
2015-08-22  6:52 ` [tip:perf/core] tools lib traceevent: Add " tip-bot for Dean Nelson

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=20150820130558.4f3a2e35@grimm.local.home \
    --to=rostedt@goodmis.org \
    --cc=a.p.zijlstra@chello.org \
    --cc=acme@kernel.org \
    --cc=dnelson@redhat.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    /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