From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751194AbcHIFPW (ORCPT ); Tue, 9 Aug 2016 01:15:22 -0400 Received: from mga11.intel.com ([192.55.52.93]:27545 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750745AbcHIFPV (ORCPT ); Tue, 9 Aug 2016 01:15:21 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,493,1464678000"; d="scan'208";a="862122619" From: Alexander Shishkin To: Vince Weaver , linux-kernel@vger.kernel.org Cc: Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo Subject: Re: perf: WARNING: kernel/events/core.c:4893 perf_mmap_close In-Reply-To: References: User-Agent: Notmuch/0.21 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Tue, 09 Aug 2016 08:15:17 +0300 Message-ID: <87k2fqmska.fsf@ashishki-desk.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Vince Weaver writes: > Hello > > running the perf_fuzzer on Haswell, this is a new warning I don't think > I've seen before. > > It works out to be this code here: > > /* this has to be the last one */ > rb_free_aux(rb); > WARN_ON_ONCE(atomic_read(&rb->aux_refcount)); > > mutex_unlock(&event->mmap_mutex); Awesome, I'll have a look. Can you tell it it was messing around with intel_bts driver from the fuzzer log? Thanks, -- Alex