diff options
author | Tristan Hume <tristan@thume.ca> | 2022-01-27 17:08:06 -0500 |
---|---|---|
committer | Peter Zijlstra <peterz@infradead.org> | 2022-02-02 13:11:40 +0100 |
commit | 1d9093457b243061a9bba23543c38726e864a643 (patch) | |
tree | 614f8cd4fe5fe58686035bedad67d331b5f492dc /kernel | |
parent | ddecd22878601a606d160680fa85802b75d92eb6 (diff) | |
download | linux-stable-1d9093457b243061a9bba23543c38726e864a643.tar.gz linux-stable-1d9093457b243061a9bba23543c38726e864a643.tar.bz2 linux-stable-1d9093457b243061a9bba23543c38726e864a643.zip |
perf/x86/intel/pt: Fix crash with stop filters in single-range mode
Add a check for !buf->single before calling pt_buffer_region_size in a
place where a missing check can cause a kernel crash.
Fixes a bug introduced by commit 670638477aed ("perf/x86/intel/pt:
Opportunistically use single range output mode"), which added a
support for PT single-range output mode. Since that commit if a PT
stop filter range is hit while tracing, the kernel will crash because
of a null pointer dereference in pt_handle_status due to calling
pt_buffer_region_size without a ToPA configured.
The commit which introduced single-range mode guarded almost all uses of
the ToPA buffer variables with checks of the buf->single variable, but
missed the case where tracing was stopped by the PT hardware, which
happens when execution hits a configured stop filter.
Tested that hitting a stop filter while PT recording successfully
records a trace with this patch but crashes without this patch.
Fixes: 670638477aed ("perf/x86/intel/pt: Opportunistically use single range output mode")
Signed-off-by: Tristan Hume <tristan@thume.ca>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Reviewed-by: Adrian Hunter <adrian.hunter@intel.com>
Cc: stable@kernel.org
Link: https://lkml.kernel.org/r/20220127220806.73664-1-tristan@thume.ca
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions