diff options
| author | Dapeng Mi <[email protected]> | 2025-10-28 06:42:14 +0000 |
|---|---|---|
| committer | Peter Zijlstra <[email protected]> | 2025-10-29 09:29:52 +0000 |
| commit | 0ba6502ce167fc3d598c08c2cc3b4ed7ca5aa251 (patch) | |
| tree | 5a2ca6c4846b33d882f2be813c19bfe86272b0c7 /lib/mpi/mpi-scan.c | |
| parent | Linux 6.18-rc3 (diff) | |
| download | kernel-0ba6502ce167fc3d598c08c2cc3b4ed7ca5aa251.tar.gz kernel-0ba6502ce167fc3d598c08c2cc3b4ed7ca5aa251.zip | |
perf/x86/intel: Fix KASAN global-out-of-bounds warning
When running "perf mem record" command on CWF, the below KASAN
global-out-of-bounds warning is seen.
==================================================================
BUG: KASAN: global-out-of-bounds in cmt_latency_data+0x176/0x1b0
Read of size 4 at addr ffffffffb721d000 by task dtlb/9850
Call Trace:
kasan_report+0xb8/0xf0
cmt_latency_data+0x176/0x1b0
setup_arch_pebs_sample_data+0xf49/0x2560
intel_pmu_drain_arch_pebs+0x577/0xb00
handle_pmi_common+0x6c4/0xc80
The issue is caused by below code in __grt_latency_data(). The code
tries to access x86_hybrid_pmu structure which doesn't exist on
non-hybrid platform like CWF.
WARN_ON_ONCE(hybrid_pmu(event->pmu)->pmu_type == hybrid_big)
So add is_hybrid() check before calling this WARN_ON_ONCE to fix the
global-out-of-bounds access issue.
Fixes: 090262439f66 ("perf/x86/intel: Rename model-specific pebs_latency_data functions")
Reported-by: Xudong Hao <[email protected]>
Signed-off-by: Dapeng Mi <[email protected]>
Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
Reviewed-by: Zide Chen <[email protected]>
Cc: [email protected]
Link: https://patch.msgid.link/[email protected]
Diffstat (limited to 'lib/mpi/mpi-scan.c')
0 files changed, 0 insertions, 0 deletions
