mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Dean Nelson <dnelson@redhat.com>
Cc: a.p.zijlstra@chello.org, mingo@redhat.com, rostedt@goodmis.org,
	acme@kernel.org, linux-kernel@vger.kernel.org, jolsa@kernel.org,
	Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH] tools lib traceevent: add checks for returned EVENT_ERROR type
Date: Fri, 7 Aug 2015 12:59:10 +0200	[thread overview]
Message-ID: <20150807105910.GE8624@krava.brq.redhat.com> (raw)
In-Reply-To: <20150803170804.22235.88475.email-sent-by-dnelson@teal>

On Mon, Aug 03, 2015 at 01:08:05PM -0400, Dean Nelson 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 ~]#

hum, what kernel are you running on? I dont see that warning
on my system:

[jolsa@krava perf]$ sudo ./perf stat -e kmem:mm_page_alloc -a sleep 1

 Performance counter stats for 'system wide':

               227      kmem:mm_page_alloc                                          

       1.000762466 seconds time elapsed

Cc-ing Namhyung


jirka

> 
> 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.
> 
> Signed-off-by: Dean Nelson <dnelson@redhat.com>
> ---
>  tools/lib/traceevent/event-parse.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/tools/lib/traceevent/event-parse.c b/tools/lib/traceevent/event-parse.c
> index cc25f05..72e2933 100644
> --- a/tools/lib/traceevent/event-parse.c
> +++ b/tools/lib/traceevent/event-parse.c
> @@ -1680,6 +1680,9 @@ process_cond(struct event_format *event, struct print_arg *top, char **tok)
>  	type = process_arg(event, left, &token);
>  
>   again:
> +	if (type == EVENT_ERROR)
> +		goto out_free;
> +
>  	/* Handle other operations in the arguments */
>  	if (type == EVENT_OP && strcmp(token, ":") != 0) {
>  		type = process_op(event, left, &token);
> @@ -1940,7 +1943,7 @@ process_op(struct event_format *event, struct print_arg *arg, char **tok)
>  
>  		type = process_arg_token(event, right, tok, type);
>  
> -		if (right->type == PRINT_OP &&
> +		if (type != EVENT_ERROR && right->type == PRINT_OP &&
>  		    get_op_prio(arg->op.op) < get_op_prio(right->op.op)) {
>  			struct print_arg tmp;
>  

  reply	other threads:[~2015-08-07 10:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 17:08 Dean Nelson
2015-08-07 10:59 ` Jiri Olsa [this message]
2015-08-07 12:16   ` Namhyung Kim
2015-08-07 13:02     ` Dean Nelson
2015-08-09  2:38       ` Namhyung Kim
2015-08-07 13:01   ` Dean Nelson
2015-08-09  3:10   ` Namhyung Kim
2015-08-10 12:41     ` 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=20150807105910.GE8624@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --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 \
    --cc=rostedt@goodmis.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

Powered by JetHome