public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Jin, Yao" <yao.jin@linux.intel.com>
Cc: John Garry <john.garry@huawei.com>,
	jolsa@kernel.org, peterz@infradead.org, mingo@redhat.com,
	alexander.shishkin@linux.intel.com, Linux-kernel@vger.kernel.org,
	ak@linux.intel.com, kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH] perf metricgroup: Fix segmentation fault for metrics with no pmu event
Date: Wed, 3 Feb 2021 12:36:29 -0300	[thread overview]
Message-ID: <20210203153629.GD854763@kernel.org> (raw)
In-Reply-To: <c73fff2c-8525-f496-66da-2cb4a8ccbf94@linux.intel.com>

Em Wed, Feb 03, 2021 at 08:46:52AM +0800, Jin, Yao escreveu:
> On 2/2/2021 4:15 PM, John Garry wrote:
> > On 02/02/2021 02:24, Jin Yao wrote:
> > > It causes the segmentation fault. Now check the pmu_name before strcmp.

> > > Fixes: c2337d67199a("perf metricgroup: Fix metrics using aliases covering multiple PMUs")
> > > Signed-off-by: Jin Yao <yao.jin@linux.intel.com>

> > This should be fixed in v5.11-rc6 - please check it.

> > 9c880c24cb0d perf metricgroup: Fix for metrics containing duration_time
 
> Oh, I see, your patch is in Arnaldo's perf/urgent branch. Sorry about that,
> I just tested Arnaldo's perf/core branch. :(

As soon as I finish processing patches today and get perf/core thru the
usual set of tests, it'll all be in perf/core.

- Arnaldo

      parent reply	other threads:[~2021-02-03 15:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02  2:24 [PATCH] perf metricgroup: Fix segmentation fault for metrics with no pmu event Jin Yao
2021-02-02  8:15 ` John Garry
2021-02-03  0:46   ` Jin, Yao
2021-02-03  8:28     ` John Garry
2021-03-05 17:35       ` Arnaldo Carvalho de Melo
2021-02-03 15:36     ` Arnaldo Carvalho de Melo [this message]

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=20210203153629.GD854763@kernel.org \
    --to=acme@kernel.org \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=john.garry@huawei.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@intel.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=yao.jin@intel.com \
    --cc=yao.jin@linux.intel.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