diff options
| author | Tristan Hume <[email protected]> | 2022-01-27 22:08:06 +0000 |
|---|---|---|
| committer | Peter Zijlstra <[email protected]> | 2022-02-02 12:11:40 +0000 |
| commit | 1d9093457b243061a9bba23543c38726e864a643 (patch) | |
| tree | 614f8cd4fe5fe58686035bedad67d331b5f492dc /lib/test_overflow.c | |
| parent | perf: uapi: Document perf_event_attr::sig_data truncation on 32 bit architect... (diff) | |
| download | kernel-1d9093457b243061a9bba23543c38726e864a643.tar.gz kernel-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 <[email protected]>
Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
Reviewed-by: Adrian Hunter <[email protected]>
Cc: [email protected]
Link: https://lkml.kernel.org/r/[email protected]
Diffstat (limited to 'lib/test_overflow.c')
0 files changed, 0 insertions, 0 deletions
