linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Liang, Kan" <kan.liang@intel.com>
Cc: "jolsa@kernel.org" <jolsa@kernel.org>,
	"ak@linux.intel.com" <ak@linux.intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] perf,tools: fix core dump caused by per-socket/core system-wide stat
Date: Tue, 20 Oct 2015 12:00:10 -0300	[thread overview]
Message-ID: <20151020150010.GE5119@kernel.org> (raw)
In-Reply-To: <37D7C6CF3E00A74B8858931C1DB2F07701972415@SHSMSX103.ccr.corp.intel.com>

Em Mon, Oct 19, 2015 at 10:22:51PM +0000, Liang, Kan escreveu:
> Hi Arnaldo
> 
> Here is one more fix for perf/core need to be pulled.

Thanks for the reminder, tried to reproduce on a two socket system,
couldn't, but the fix is obvious enough, thanks, applied.

- Arnaldo
 
> Thanks,
> Kan
> 
> > 
> > On Fri, Oct 09, 2015 at 06:59:23AM -0400, kan.liang@intel.com wrote:
> > > From: Kan Liang <kan.liang@intel.com>
> > >
> > > Perf will core dump if --per-socket/core -a are applied for perf stat.
> > >
> > > The root cause is that cpu_map__build_map set refcnt of evlist's
> > > cpu_map to 1.
> > > It should set refcnt for the newly created cpu_map, not evlist's
> > > cpu_map.
> > >
> > > Here is the example:
> > >
> > > perf stat -e cycles --per-socket -a sleep 1
> > >
> > >  Performance counter stats for 'system wide':
> > >
> > > S0       36         30,196,257      cycles
> > > S1       28         15,823,536      cycles
> > >
> > >        1.001126828 seconds time elapsed
> > >
> > > *** Error in `./perf': corrupted double-linked list:
> > > 0x00000000021f9090
> > > ***
> > > ======= Backtrace: =========
> > > /lib64/libc.so.6[0x3002e7bbe7]
> > > /lib64/libc.so.6[0x3002e7d2b5]
> > > ./perf(perf_evsel__delete+0x28)[0x485bdd]
> > > ./perf[0x4800e8]
> > > ./perf(perf_evlist__delete+0x5e)[0x482cd5]
> > > ./perf(cmd_stat+0xf25)[0x432328]
> > > ./perf[0x4768e0]
> > > ./perf[0x476ad6]
> > > ./perf[0x476b41]
> > > ./perf(main+0x1d0)[0x476db2]
> > > /lib64/libc.so.6(__libc_start_main+0xf5)[0x3002e21b45]
> > > ./perf[0x4202c5]
> > >
> > > Signed-off-by: Kan Liang <kan.liang@intel.com>
> > > ---
> > >  tools/perf/util/cpumap.c | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/tools/perf/util/cpumap.c b/tools/perf/util/cpumap.c index
> > > c51c29f..dfc1f0b 100644
> > > --- a/tools/perf/util/cpumap.c
> > > +++ b/tools/perf/util/cpumap.c
> > > @@ -284,7 +284,7 @@ static int cpu_map__build_map(struct cpu_map
> > *cpus, struct cpu_map **res,
> > >  	/* ensure we process id in increasing order */
> > >  	qsort(c->map, c->nr, sizeof(int), cmp_ids);
> > >
> > > -	atomic_set(&cpus->refcnt, 1);
> > > +	atomic_set(&c->refcnt, 1);
> > 
> > ouch ;-)
> > 
> > Acked-by: Jiri Olsa <jolsa@kernel.org>
> > 
> > thanks,
> > jirka

  reply	other threads:[~2015-10-20 15:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09 10:59 [PATCH 1/1] perf,tools: fix core dump caused by per-socket/core system-wide stat kan.liang
2015-10-09 20:59 ` Jiri Olsa
2015-10-19 22:22   ` Liang, Kan
2015-10-20 15:00     ` Arnaldo Carvalho de Melo [this message]
2015-10-22  9:22 ` [tip:perf/core] perf cpu_map: Fix core dump caused by per-socket/ core " tip-bot for Kan Liang

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=20151020150010.GE5119@kernel.org \
    --to=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@intel.com \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).