From: Taeung Song <treeze.taeung@gmail.com>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Wang Nan <wangnan0@huawei.com>, Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH v2 3/4] perf tools: Check NULL after zalloc() and Use zfree() instead of free() in parse-events.c
Date: Wed, 1 Feb 2017 17:04:08 +0900 [thread overview]
Message-ID: <2650b144-8a7a-e902-3012-4d1167e188e4@gmail.com> (raw)
In-Reply-To: <20170131132335.GE4491@kernel.org>
Sorry I'm late..
I got it!
I'll send v3 with changed patches !!
Thanks,
Taeung
On 01/31/2017 10:23 PM, Arnaldo Carvalho de Melo wrote:
> Em Tue, Jan 31, 2017 at 08:38:30PM +0900, Taeung Song escreveu:
>> Currently there are several parts not checking NULL
>> after allocating with zalloc() or asigning NULL value
>> to a pointer variable after doing free().
>>
>> So I fill in code checking NULL and
>> use zfree() instead of free().
>
> You are doing more than one thing on this patch, don't do that.
>
> Please split it for the "no functional changes" parts, i.e. things like
>
> - free(path);
> - path = NULL;
> + zfree(&path);
>
> From the ones that _change_ logic, like the first hunk:
>
> path = zalloc(sizeof(*path));
> + if (!path)
> + return NULL;
> path->system = malloc(MAX_EVENT_LENGTH);
> if (!path->system) {
> free(path);
>
> This one as well changes logic:
>
> @@ -1563,7 +1563,7 @@ perf_pmu__parse_check(const char *name)
> r = bsearch(&p, perf_pmu_events_list,
> (size_t) perf_pmu_events_list_num,
> sizeof(struct perf_pmu_event_symbol), comp_pmu);
> - free(p.symbol);
> + zfree(&p.symbol);
> return r ? r->type : PMU_EVENT_SYMBOL_ERR;
>
>
>> Cc: Namhyung Kim <namhyung@kernel.org>
>> Cc: Jiri Olsa <jolsa@redhat.com>
>> Signed-off-by: Taeung Song <treeze.taeung@gmail.com>
>> ---
>> tools/perf/util/parse-events.c | 20 ++++++++++----------
>> 1 file changed, 10 insertions(+), 10 deletions(-)
>>
>> diff --git a/tools/perf/util/parse-events.c b/tools/perf/util/parse-events.c
>> index 3c876b8..87a3e5a 100644
>> --- a/tools/perf/util/parse-events.c
>> +++ b/tools/perf/util/parse-events.c
>> @@ -211,6 +211,8 @@ struct tracepoint_path *tracepoint_id_to_path(u64 config)
>> closedir(evt_dir);
>> closedir(sys_dir);
>> path = zalloc(sizeof(*path));
>> + if (!path)
>> + return NULL;
>> path->system = malloc(MAX_EVENT_LENGTH);
>> if (!path->system) {
>> free(path);
>> @@ -252,8 +254,7 @@ struct tracepoint_path *tracepoint_name_to_path(const char *name)
>> if (path->system == NULL || path->name == NULL) {
>> zfree(&path->system);
>> zfree(&path->name);
>> - free(path);
>> - path = NULL;
>> + zfree(&path);
>> }
>>
>> return path;
>> @@ -1477,10 +1478,9 @@ static void perf_pmu__parse_cleanup(void)
>>
>> for (i = 0; i < perf_pmu_events_list_num; i++) {
>> p = perf_pmu_events_list + i;
>> - free(p->symbol);
>> + zfree(&p->symbol);
>> }
>> - free(perf_pmu_events_list);
>> - perf_pmu_events_list = NULL;
>> + zfree(&perf_pmu_events_list);
>> perf_pmu_events_list_num = 0;
>> }
>> }
>> @@ -1563,7 +1563,7 @@ perf_pmu__parse_check(const char *name)
>> r = bsearch(&p, perf_pmu_events_list,
>> (size_t) perf_pmu_events_list_num,
>> sizeof(struct perf_pmu_event_symbol), comp_pmu);
>> - free(p.symbol);
>> + zfree(&p.symbol);
>> return r ? r->type : PMU_EVENT_SYMBOL_ERR;
>> }
>>
>> @@ -1710,8 +1710,8 @@ static void parse_events_print_error(struct parse_events_error *err,
>> fprintf(stderr, "%*s\\___ %s\n", idx + 1, "", err->str);
>> if (err->help)
>> fprintf(stderr, "\n%s\n", err->help);
>> - free(err->str);
>> - free(err->help);
>> + zfree(&err->str);
>> + zfree(&err->help);
>> }
>>
>> fprintf(stderr, "Run 'perf list' for a list of valid events\n");
>> @@ -2406,7 +2406,7 @@ void parse_events_terms__purge(struct list_head *terms)
>>
>> list_for_each_entry_safe(term, h, terms, list) {
>> if (term->array.nr_ranges)
>> - free(term->array.ranges);
>> + zfree(&term->array.ranges);
>> list_del_init(&term->list);
>> free(term);
>> }
>> @@ -2422,7 +2422,7 @@ void parse_events_terms__delete(struct list_head *terms)
>>
>> void parse_events__clear_array(struct parse_events_array *a)
>> {
>> - free(a->ranges);
>> + zfree(&a->ranges);
>> }
>>
>> void parse_events_evlist_error(struct parse_events_evlist *data,
>> --
>> 2.7.4
next prev parent reply other threads:[~2017-02-01 8:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 11:38 [PATCH v2 0/4] Add ftrace config and refactor several parts Taeung Song
2017-01-31 11:38 ` [PATCH v2 1/4] perf tools: Create for_each_event macro for tracepoints iteration Taeung Song
2017-01-31 12:21 ` Arnaldo Carvalho de Melo
2017-01-31 12:23 ` Arnaldo Carvalho de Melo
2017-01-31 17:32 ` Steven Rostedt
2017-02-01 7:02 ` Taeung Song
2017-02-01 14:43 ` [tip:perf/core] " tip-bot for Taeung Song
2017-01-31 11:38 ` [PATCH v2 2/4] perf ftrace: Add ftrace.tracer config option Taeung Song
2017-01-31 12:46 ` Arnaldo Carvalho de Melo
2017-01-31 13:15 ` Arnaldo Carvalho de Melo
2017-02-01 7:27 ` Taeung Song
2017-02-01 14:43 ` [tip:perf/core] " tip-bot for Taeung Song
2017-01-31 11:38 ` [PATCH v2 3/4] perf tools: Check NULL after zalloc() and Use zfree() instead of free() in parse-events.c Taeung Song
2017-01-31 13:23 ` Arnaldo Carvalho de Melo
2017-02-01 8:04 ` Taeung Song [this message]
2017-01-31 11:38 ` [PATCH v2 4/4] perf tools: Increase index if perf_evsel__new_idx() succeeded Taeung Song
2017-01-31 13:25 ` Arnaldo Carvalho de Melo
2017-02-01 8:04 ` Taeung Song
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=2650b144-8a7a-e902-3012-4d1167e188e4@gmail.com \
--to=treeze.taeung@gmail.com \
--cc=arnaldo.melo@gmail.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=wangnan0@huawei.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
Powered by JetHome