From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933798AbcIOHPJ (ORCPT ); Thu, 15 Sep 2016 03:15:09 -0400 Received: from merlin.infradead.org ([205.233.59.134]:51134 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759534AbcIOHPI (ORCPT ); Thu, 15 Sep 2016 03:15:08 -0400 Date: Thu, 15 Sep 2016 09:15:00 +0200 From: Peter Zijlstra To: Vince Weaver Cc: linux-kernel@vger.kernel.org, Alexander Shishkin , Stephane Eranian , Ingo Molnar Subject: Re: perf: perf_fuzzer lockup in perf_cgroup_attach Message-ID: <20160915071500.GM5008@twins.programming.kicks-ass.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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?