[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170130123929.GA11887@krava>
Date: Mon, 30 Jan 2017 13:39:29 +0100
From: Jiri Olsa <jolsa@...hat.com>
To: Taeung Song <treeze.taeung@...il.com>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
linux-kernel@...r.kernel.org, Jiri Olsa <jolsa@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Wang Nan <wangnan0@...wei.com>
Subject: Re: [PATCH 1/2] perf tools: Use zfree() instead of free() in
parse-events.c
On Mon, Jan 30, 2017 at 07:37:58PM +0900, Taeung Song wrote:
>
>
> On 01/30/2017 06:01 PM, Jiri Olsa wrote:
> > On Mon, Jan 30, 2017 at 02:23:38PM +0900, Taeung Song wrote:
> > > 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().
> >
> > can't see directly reasons for zfree usage,
> > but it looks reasonable.. do you have any
> > crash reports due to missing zfree?
>
> No, Just I read source code util/parse-events.c
> And I found several insufficiency, shortcoming
> not checking NULL or assigning NULL value to a pointer
> variable after free().
> So, I think we can use zfree() insteadof free()+assigning NULL.
ok
>
> Change commit message to be more appropriate ?
that's always good idea ;-)
thanks,
jirka
>
> Thanks,
> Taeung
>
Powered by blists - more mailing lists