From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Vince Weaver <vincent.weaver@maine.edu>,
Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
torvalds@linux-foundation.org
Subject: Re: perf: perf_fuzzer triggers NULL pointer dereference
Date: Thu, 08 Nov 2018 18:14:47 +0200 [thread overview]
Message-ID: <87a7mj5yx4.fsf@ashishki-desk.ger.corp.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1811081100490.7406@macbook-air>
Vince Weaver <vincent.weaver@maine.edu> writes:
> On Thu, 8 Nov 2018, Vince Weaver wrote:
>
>> [91760.326510] BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
>> [91760.334876] PGD 0 P4D 0
>> [91760.337596] Oops: 0000 [#1] SMP PTI
>> [91760.341332] CPU: 6 PID: 0 Comm: swapper/6 Tainted: G W 4.20.0-rc1+ #119
>> [91760.349816] Hardware name: LENOVO 10AM000AUS/SHARKBAY, BIOS FBKT72AUS 01/26/2014
>> [91760.357723] RIP: 0010:perf_prepare_sample+0x82/0x4a0
>
> so what's the best way to do the equivelent of addr2line on something like
> this, now that we aren't allowed to know the RIP anymore?
scripts/decode_stacktrace.sh works most of the time.
Sounds like BTS needs fixing up again. Thanks for looking at it though!
Regards,
--
Alex
next prev parent reply other threads:[~2018-11-08 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 15:46 Vince Weaver
2018-11-08 16:05 ` Vince Weaver
2018-11-08 16:14 ` Alexander Shishkin [this message]
2018-11-08 16:46 ` Vince Weaver
2018-11-09 16:38 ` 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=87a7mj5yx4.fsf@ashishki-desk.ger.corp.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=acme@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=vincent.weaver@maine.edu \
/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
all inboxes | Powered by JetHome®