From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Chris Phlipot <cphlipot0@gmail.com>, Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] Fixes: cfc8874a485 ("perf script: Process cpu/threads maps")
Date: Wed, 9 Mar 2016 10:35:27 -0300 [thread overview]
Message-ID: <20160309133527.GA3529@kernel.org> (raw)
In-Reply-To: <20160309080246.GA13837@krava.redhat.com>
Em Wed, Mar 09, 2016 at 09:02:46AM +0100, Jiri Olsa escreveu:
> On Tue, Mar 08, 2016 at 09:11:54PM -0800, Chris Phlipot wrote:
> > fix the perf script python database export crash.
> > Remove the union in evsel so that the database id and priv pointer can be
> > used simultainously without conflicting and crashing.
> >
> > Detailed Description for the fixed bug follows:
> >
> > perf script crashes with a segmentaiton fault on user space tool version
> > 4.5.rc7.ge2857b when using the python database export API. It works
> > properly in 4.4 and prior versions.
> >
> > the crash fist appeared in
> > cfc8874a485 ("perf script: Process cpu/threads maps")
>
> ouch, missed this one..
>
> Acked-by: Jiri Olsa <jolsa@kernel.org>
Thanks, applied.
- Arnaldo
next prev parent reply other threads:[~2016-03-09 13:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 5:11 [PATCH 1/1] Fixes: cfc8874a485 ("perf script: Process cpu/threads maps") Chris Phlipot
2016-03-09 8:02 ` Jiri Olsa
2016-03-09 13:35 ` Arnaldo Carvalho de Melo [this message]
2016-03-11 8:46 ` [tip:perf/core] perf tools: Fix perf script python database export crash tip-bot for Chris Phlipot
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=20160309133527.GA3529@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=cphlipot0@gmail.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).