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-next>] [day] [month] [year] [list]
Message-Id: <1434024837-9916-1-git-send-email-alexander.shishkin@linux.intel.com>
Date:	Thu, 11 Jun 2015 15:13:55 +0300
From:	Alexander Shishkin <alexander.shishkin@...ux.intel.com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Ingo Molnar <mingo@...hat.com>
Cc:	linux-kernel@...r.kernel.org, adrian.hunter@...el.com,
	x86@...nel.org, hpa@...or.com, acme@...radead.org,
	Alexander Shishkin <alexander.shishkin@...ux.intel.com>
Subject: [PATCH 0/2] perf/x86/intel: Fixes for PT and BTS

Hi Peter and Ingo,

I have here two fixes for 4.1, both of which are basically results
of not testing code properly with the NMI watchdog disabled, so one
lesson learned here.

One bug results in trace data loss and unknown NMI warnings and the
other one is a NULL pointer dereference. The latter might need to be
revisited in the future as we're now handling PT PMIs from
intel_pmu_handle_irq() and we might want to change that. On the other
hand, PT and x86_pmu share the PMI status register, so from that angle
it kind of makes sense. But until such time as we decide to sort it
out, the proposed fix should do nicely.

Alexander Shishkin (2):
  perf/x86/intel/bts: Fix DS area sharing with x86_pmu events
  perf/x86/intel: Fix PMI handling for Intel PT

 arch/x86/kernel/cpu/perf_event.c           | 70 +++++++++++++++++++++---------
 arch/x86/kernel/cpu/perf_event.h           |  4 ++
 arch/x86/kernel/cpu/perf_event_intel_bts.c |  9 ++++
 3 files changed, 63 insertions(+), 20 deletions(-)

-- 
2.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ