From: Namhyung Kim <namhyung@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung.kim@lge.com>,
LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 5/9] perf util: Handle failure case in trace_report()
Date: Wed, 20 Mar 2013 10:12:41 +0900 [thread overview]
Message-ID: <87ip4mj2ly.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <1363704473.5938.25.camel@gandalf.local.home> (Steven Rostedt's message of "Tue, 19 Mar 2013 10:47:53 -0400")
On Tue, 19 Mar 2013 10:47:53 -0400, Steven Rostedt wrote:
> On Tue, 2013-03-19 at 17:53 +0900, Namhyung Kim wrote:
>
>> @@ -3100,7 +3105,7 @@ int perf_event__process_tracing_data(union perf_event *event,
>> }
>> }
>>
>> - if (size_read + padding != size) {
>> + if (size_read + padding != size || session->pevent == NULL) {
>> pr_err("%s: tracing data size mismatch", __func__);
>
> This is a strange error to give when pevent is NULL. Could have been a
> malloc failure.
Hmm.. right. I was just too lazy. ;)
Will break NULL check and print "failed to process tracing data" as we
set it to NULL if something broken.
>
>
>> return -1;
>> }
>> diff --git a/tools/perf/util/trace-event-read.c b/tools/perf/util/trace-event-read.c
>> index 7cb24635adf2..129362b97ca5 100644
>> --- a/tools/perf/util/trace-event-read.c
>> +++ b/tools/perf/util/trace-event-read.c
>> @@ -293,7 +293,10 @@ ssize_t trace_report(int fd, struct pevent **ppevent, bool __repipe)
>> int show_version = 0;
>> int show_funcs = 0;
>> int show_printk = 0;
>> - ssize_t size;
>> + ssize_t size = -1;
>> + struct pevent *pevent;
>> +
>> + *ppevent = NULL;
>>
>> calc_data_size = 1;
>> repipe = __repipe;
>> @@ -317,34 +320,38 @@ ssize_t trace_report(int fd, struct pevent **ppevent, bool __repipe)
>> file_bigendian = buf[0];
>> host_bigendian = bigendian();
>>
>> - *ppevent = read_trace_init(file_bigendian, host_bigendian);
>> - if (*ppevent == NULL)
>> - die("read_trace_init failed");
>> + pevent = read_trace_init(file_bigendian, host_bigendian);
>> + if (pevent == NULL) {
>
> Shouldn't we still set *ppevent to NULL? Or will the user now need to
> make sure that its pevent is NULL and always check for error?
I thought it's impossible to check return value for error since we don't
know how large a tracing data is, so I decided to init *ppevent to NULL
at the beginning and set it to a valid pevent right before return. Thus
user need to check NULL before using it.
In the above case of perf_event__process_tracing_data(), it's a pipe
mode and we can know its size since it's saved in a temp file.
Thanks,
Namhyung
next prev parent reply other threads:[~2013-03-20 1:12 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 8:53 [PATCHSET 0/9] perf util: Cleanup die() and its friends Namhyung Kim
2013-03-19 8:53 ` [PATCH 1/9] perf util: Let get_tracing_file() can return NULL Namhyung Kim
2013-03-19 13:54 ` Steven Rostedt
2013-03-20 0:53 ` Namhyung Kim
2013-03-19 8:53 ` [PATCH 2/9] perf util: Get rid of malloc_or_die() in trace-event-info.c Namhyung Kim
2013-03-19 8:53 ` [PATCH 3/9] perf util: Get rid of write_or_die() from trace-event-info.c Namhyung Kim
2013-03-19 14:35 ` Steven Rostedt
2013-03-19 14:49 ` Peter Zijlstra
2013-03-19 14:59 ` Steven Rostedt
2013-03-19 15:04 ` Peter Zijlstra
2013-03-20 0:57 ` Namhyung Kim
2013-03-19 8:53 ` [PATCH 4/9] perf util: Get rid of die() calls " Namhyung Kim
2013-03-19 8:53 ` [PATCH 5/9] perf util: Handle failure case in trace_report() Namhyung Kim
2013-03-19 14:47 ` Steven Rostedt
2013-03-20 1:12 ` Namhyung Kim [this message]
2013-03-20 1:54 ` Steven Rostedt
2013-03-19 8:53 ` [PATCH 6/9] perf util: Get rid of malloc_or_die() in trace-event-read.c Namhyung Kim
2013-03-19 14:50 ` Steven Rostedt
2013-03-20 1:14 ` Namhyung Kim
2013-03-20 1:55 ` Steven Rostedt
2013-03-20 3:00 ` Namhyung Kim
2013-03-20 3:13 ` Steven Rostedt
2013-03-20 13:04 ` Arnaldo Carvalho de Melo
2013-03-19 8:53 ` [PATCH 7/9] perf util: Get rid of read_or_die() " Namhyung Kim
2013-03-19 14:54 ` Steven Rostedt
2013-03-20 1:24 ` Namhyung Kim
2013-03-20 1:59 ` Steven Rostedt
2013-03-19 8:53 ` [PATCH 8/9] perf util: Get rid of die() calls in trace-data-read.c Namhyung Kim
2013-03-19 14:55 ` Steven Rostedt
2013-03-20 1:25 ` Namhyung Kim
2013-03-20 13:27 ` Arnaldo Carvalho de Melo
2013-03-19 8:53 ` [PATCH 9/9] perf util: Cleanup calc_data_size logic Namhyung Kim
-- strict thread matches above, loose matches on Subject: below --
2013-03-21 7:18 [PATCHSET 0/9] perf util: Cleanup die() and its friends (v2) Namhyung Kim
2013-03-21 7:18 ` [PATCH 5/9] perf util: Handle failure case in trace_report() Namhyung Kim
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=87ip4mj2ly.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.