public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
	changbin.du@intel.com, peterz@infradead.org, mingo@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] perf: fix double free at function perf_hpp__reset_output_field
Date: Mon, 10 Apr 2017 10:39:50 +0200	[thread overview]
Message-ID: <20170410083950.GD25354@krava> (raw)
In-Reply-To: <20170404151940.GD12903@kernel.org>

On Tue, Apr 04, 2017 at 12:19:40PM -0300, Arnaldo Carvalho de Melo wrote:

SNIP

> > ---
> >  tools/perf/ui/hist.c | 25 +++++++++++++++----------
> >  1 file changed, 15 insertions(+), 10 deletions(-)
> > 
> > diff --git a/tools/perf/ui/hist.c b/tools/perf/ui/hist.c
> > index 5d632dc..f94b301 100644
> > --- a/tools/perf/ui/hist.c
> > +++ b/tools/perf/ui/hist.c
> > @@ -609,20 +609,25 @@ static void fmt_free(struct perf_hpp_fmt *fmt)
> >  
> >  void perf_hpp__reset_output_field(struct perf_hpp_list *list)
> >  {
> > -	struct perf_hpp_fmt *fmt, *tmp;
> > +	struct perf_hpp_fmt *field_fmt, *sort_fmt, *tmp1, *tmp2;
> >  
> >  	/* reset output fields */
> > -	perf_hpp_list__for_each_format_safe(list, fmt, tmp) {
> > -		list_del_init(&fmt->list);
> > -		list_del_init(&fmt->sort_list);
> > -		fmt_free(fmt);
> > +	perf_hpp_list__for_each_format_safe(list, field_fmt, tmp1) {
> > +		list_del_init(&field_fmt->list);
> > +		/* reset sort keys */
> > +		perf_hpp_list__for_each_sort_list_safe(list, sort_fmt, tmp2) {
> > +			if (field_fmt == sort_fmt) {
> > +				list_del_init(&field_fmt->sort_list);
> > +				break;
> > +			}
> > +		}

I agree with Namhyung in here.. seems like the only thing you
added is to check if the field_fmt was also linked in as a sort
entry before you call list_del_init on it

which I think should be also done with list_empty function, but
more importantly I dont see a reason for that.. list_del_init
call should be fine on empty list

please describe the issue in more details, perhaps we'ew missing
something

jirka

  parent reply	other threads:[~2017-04-10  8:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15  2:16 [PATCH] perf: double free at function perf_hpp__reset_output_field changbin.du
2017-03-27  6:22 ` [PATCH v2] perf: fix " changbin.du
2017-04-04 15:19   ` Arnaldo Carvalho de Melo
2017-04-04 15:34     ` Namhyung Kim
2017-04-04 15:51       ` Arnaldo Carvalho de Melo
2017-04-05  2:44         ` Du, Changbin
2017-04-09 17:05           ` Jiri Olsa
2017-04-10  2:13             ` Du, Changbin
2017-04-10  8:39     ` Jiri Olsa [this message]
2017-04-10 10:21       ` Du, Changbin
2017-04-10 11:33         ` Jiri Olsa
2017-04-11  3:06           ` Du, Changbin
2017-04-11  7:35             ` Jiri Olsa
2017-04-11  8:25               ` Du, Changbin
2017-04-11 10:05                 ` Jiri Olsa
2017-04-11 10:13                   ` Du, Changbin
2017-04-11 10:32                     ` Jiri Olsa
2017-04-12  1:48                       ` Du, Changbin
2017-05-31  7:05                         ` Du, Changbin
2017-05-31  7:19                           ` Jiri Olsa

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=20170410083950.GD25354@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=changbin.du@intel.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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