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]

Date:   Thu, 15 Sep 2016 09:15:00 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Vince Weaver <vincent.weaver@...ne.edu>
Cc:     linux-kernel@...r.kernel.org,
        Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
        Stephane Eranian <eranian@...gle.com>,
        Ingo Molnar <mingo@...nel.org>
Subject: Re: perf: perf_fuzzer lockup in perf_cgroup_attach

On Wed, Sep 14, 2016 at 10:43:29PM -0400, Vince Weaver 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.
> 
> The best I can tell things are getting wedged somehow in 
> perf_cgroup_switch() while interrupts are disabled.  Interrupts are never 
> getting re-enabled, causing the RCU and NMI watchdogs to trigger (and more 
> alarming things like the SATA bus resetting).

How do you go about using cgroups? Do you set them up yourself, does the
fuzzer do so?