linux-kernel - Re: perf: perf_fuzzer lockup in perf_cgroup

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160915121014.ox5ytlplt7wz5cpk@treble>
Date:   Thu, 15 Sep 2016 07:10:14 -0500
From:   Josh Poimboeuf <jpoimboe@...hat.com>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     Stephane Eranian <eranian@...gle.com>,
        Vince Weaver <vincent.weaver@...ne.edu>,
        LKML <linux-kernel@...r.kernel.org>,
        Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
        Ingo Molnar <mingo@...nel.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: perf: perf_fuzzer lockup in perf_cgroup_attach

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@...ne.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