From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933213AbcHWI56 (ORCPT ); Tue, 23 Aug 2016 04:57:58 -0400 Received: from mga05.intel.com ([192.55.52.43]:26231 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933138AbcHWI5y (ORCPT ); Tue, 23 Aug 2016 04:57:54 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,565,1464678000"; d="scan'208";a="1045771375" From: Alexander Shishkin To: Peter Zijlstra Cc: Ingo Molnar , linux-kernel@vger.kernel.org, vince@deater.net, eranian@google.com, Arnaldo Carvalho de Melo , Alexander Shishkin Subject: [PATCH 0/3] perf, bts: Fallout from the fuzzer for perf/urgent Date: Tue, 23 Aug 2016 11:54:31 +0300 Message-Id: <1471942474-1854-1-git-send-email-alexander.shishkin@linux.intel.com> X-Mailer: git-send-email 2.8.0.rc3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Recently Vince has reported warnings and panics coming from the general direction of AUX tracing. I found two bugs which manifest similarly, one in intel_bts driver and one in AUX unmapping path. Both are triggered by racing SET_OUTPUT against mmap_close while running AUX tracing. I have a test case that set fire to the kernel within a few seconds by doing this, which I can share if anyone cares. These are all good candidates for 4.7-stable and the BTS ones can be theoretically backported further. Alexander Shishkin (3): perf/x86/intel/bts: Fix confused ordering of PMU callbacks perf/x86/intel/bts: Kill a silly warning perf: Fix a race between mmap_close and set_output of AUX events arch/x86/events/intel/bts.c | 87 +++++++++++++++++++++++++++++++++------------ kernel/events/core.c | 31 ++++++++++++---- 2 files changed, 89 insertions(+), 29 deletions(-) -- 2.8.1