From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Stephane Eranian <eranian@google.com>,
Vince Weaver <vincent.weaver@maine.edu>,
LKML <linux-kernel@vger.kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ingo Molnar <mingo@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: perf: perf_fuzzer lockup in perf_cgroup_attach
Date: Thu, 15 Sep 2016 07:10:14 -0500 [thread overview]
Message-ID: <20160915121014.ox5ytlplt7wz5cpk@treble> (raw)
In-Reply-To: <20160915072425.GN5008@twins.programming.kicks-ass.net>
On Thu, Sep 15, 2016 at 09:24:25AM +0200, Peter Zijlstra wrote:
> On Wed, Sep 14, 2016 at 10:35:49PM -0700, Stephane Eranian wrote:
> > On Wed, Sep 14, 2016 at 7:43 PM, Vince Weaver <vincent.weaver@maine.edu> wrote:
> > >
> > > so the skylake that was fuzzing finally is mostly locked up.
> > >
> > > Really hard to tell what's going, especially as KASLR made looking up the
> > > addresses a big pain.
> > >
> > I would think there is a way to disable KASLR for this kind of testing!
>
> I always kill CONFIG_RANDOMIZE_BASE, but there's also talk of killing
> the address print entirely.. :-(
>
> https://lkml.kernel.org/r/20160831165303.tvcudt7wkpechuqt@treble
So you should be able to do something like:
echo "list *driver_probe_device+0x223" |gdb vmlinux |grep "is in"
Though that's admittedly quite a bit slower than addr2line.
--
Josh
next prev parent reply other threads:[~2016-09-15 12:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 2:43 perf: perf_fuzzer lockup in perf_cgroup_attach Vince Weaver
2016-09-15 5:35 ` Stephane Eranian
2016-09-15 7:24 ` Peter Zijlstra
2016-09-15 12:10 ` Josh Poimboeuf [this message]
2016-09-16 14:48 ` [PATCH] scripts: add script for translating stack dump function offsets Josh Poimboeuf
2016-09-16 18:12 ` Linus Torvalds
2016-09-16 19:17 ` Josh Poimboeuf
2016-09-16 19:26 ` Linus Torvalds
2016-09-16 21:26 ` [PATCH v2] " Josh Poimboeuf
2016-09-17 0:09 ` Linus Torvalds
2016-09-17 0:42 ` Josh Poimboeuf
2016-09-17 1:59 ` Linus Torvalds
2016-09-17 2:31 ` Linus Torvalds
2016-09-17 18:45 ` Josh Poimboeuf
2016-09-19 15:52 ` [PATCH v3] scripts: add script for translating stack dump function Josh Poimboeuf
2016-09-19 18:56 ` Linus Torvalds
2016-09-19 19:15 ` Linus Torvalds
2016-09-19 19:28 ` Josh Poimboeuf
2016-09-19 20:00 ` Rabin Vincent
2016-09-19 20:24 ` Linus Torvalds
2016-09-19 20:56 ` Josh Poimboeuf
2016-09-19 21:02 ` Linus Torvalds
2016-09-19 21:07 ` Josh Poimboeuf
2016-09-17 1:25 ` [PATCH v2] scripts: add script for translating stack dump function offsets Peter Zijlstra
2016-09-17 8:15 ` Rabin Vincent
2016-09-17 18:48 ` Josh Poimboeuf
2016-09-17 9:11 ` [PATCH] " Vegard Nossum
2016-09-17 18:54 ` Josh Poimboeuf
2016-09-15 12:47 ` perf: perf_fuzzer lockup in perf_cgroup_attach Vince Weaver
2016-09-15 7:15 ` Peter Zijlstra
2016-09-15 12:41 ` Vince Weaver
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=20160915121014.ox5ytlplt7wz5cpk@treble \
--to=jpoimboe@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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;
as well as URLs for NNTP newsgroup(s).