public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: ak@linux•intel.com (Andi Kleen)
To: linux-arm-kernel@lists•infradead.org
Subject: perf segmentation fault from NULL dereference
Date: Wed, 26 Sep 2018 20:00:35 -0700	[thread overview]
Message-ID: <20180927030035.GF28040@tassilo.jf.intel.com> (raw)
In-Reply-To: <712b7c31-f681-7737-71e7-c028b8d2bba5@huawei.com>

> Please me let me know if a valid issue so we can get a fix in.

If it crashes it must be a valid issue of course.

But I'm not sure about your bisect. Hard to see how my patch
could cause this. Sometimes bisects go wrong. 
You verified by just reverting the patch?

First thing I would also try is to run with valgrind or ASan and see if it
reports anything.

-Andi

  reply	other threads:[~2018-09-27  3:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25 15:53 perf segmentation fault from NULL dereference John Garry
2018-09-27  3:00 ` Andi Kleen [this message]
2018-10-02 10:20   ` John Garry
2018-09-27 16:02 ` Jiri Olsa
2018-10-02 10:41   ` John Garry
2018-10-02 11:16     ` Jiri Olsa
2018-10-03 11:36       ` [PATCH] perf tools: Allocate id array in perf_event__synthesize_event_update_cpus Jiri Olsa
2018-10-03 14:08         ` John Garry
2018-10-03 14:16           ` Jiri Olsa
2018-10-03 21:20             ` [PATCH] perf tools: Store ids for events with their own cpus perf_event__synthesize_event_update_cpus Jiri Olsa
2018-10-04  9:20               ` John Garry
2018-10-09 10:00                 ` Jiri Olsa
2018-10-12 13:25                   ` John Garry
2018-10-15 19:15                     ` Arnaldo Carvalho de Melo
2018-10-16  9:10                       ` John Garry
2018-10-16 10:47                         ` 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=20180927030035.GF28040@tassilo.jf.intel.com \
    --to=ak@linux$(echo .)intel.com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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