summaryrefslogtreecommitdiffstats
path: root/arch/x86/pci
diff options
context:
space:
mode:
authorAlexander Shishkin <alexander.shishkin@linux.intel.com>2016-09-06 16:23:51 +0300
committerIngo Molnar <mingo@kernel.org>2016-09-10 11:15:37 +0200
commita9a94401c2b5805c71e39427b1af1bf1b9f67cd0 (patch)
tree07395919ca53f90bd7d2c82abd2a6b9e903678bd /arch/x86/pci
parentb79ccadd6bb10e72cf784a298ca6dc1398eb9a24 (diff)
downloadop-kernel-dev-a9a94401c2b5805c71e39427b1af1bf1b9f67cd0.zip
op-kernel-dev-a9a94401c2b5805c71e39427b1af1bf1b9f67cd0.tar.gz
perf/x86/intel/bts: Fix confused ordering of PMU callbacks
The intel_bts driver is using a CPU-local 'started' variable to order callbacks and PMIs and make sure that AUX transactions don't get messed up. However, the ordering rules in regard to this variable is a complete mess, which recently resulted in perf_fuzzer-triggered warnings and panics. The general ordering rule that is patch is enforcing is that this cpu-local variable be set only when the cpu-local AUX transaction is active; consequently, this variable is to be checked before the AUX related bits can be touched. Reported-by: Vince Weaver <vincent.weaver@maine.edu> Signed-off-by: Alexander Shishkin <alexander.shishkin@linux.intel.com> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Cc: Arnaldo Carvalho de Melo <acme@infradead.org> Cc: Arnaldo Carvalho de Melo <acme@redhat.com> Cc: Jiri Olsa <jolsa@redhat.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Stephane Eranian <eranian@google.com> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: vince@deater.net Link: http://lkml.kernel.org/r/20160906132353.19887-4-alexander.shishkin@linux.intel.com Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'arch/x86/pci')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud