From nobody Mon Feb 9 05:53:00 2026 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7F5631C5D46; Tue, 28 Oct 2025 06:44:55 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.175.65.16 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1761633897; cv=none; b=Q8NHc/bk/6sdA9aCIzJw4R6gDXJyZbyiXt/YZvRzke8TJjRdZ7E0ODAbhZ2bn5PGzPLNrNKNkCU7MdfJ6FvzOrt+5EJ8mjLxYWKvB/OqLbpXk9itG0Jja67YgChlrAeyhArjBaHZN7y2B0D/m4H51bOHr31OV9poTG7wrh7L7Vw= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1761633897; c=relaxed/simple; bh=7R93AM51irQ+2d/T+qJcF1Qkq5IbJli4SD6al94qH0o=; h=From:To:Cc:Subject:Date:Message-Id:MIME-Version; b=j983bZUWyG0oAxjtiOTZdRWi1h+uYWoo03pMGMRSkWTYpJMI8NoFZto5pjj7oBtTJpl6QQcZVHmr/cSVtQ0zvrcM2QnosbBB38BqV3zzwCqx6VNYe2uNb0qvUQM5+iVuI/9/LQFZUwwbDoajePZctNvhi+0ectUSefVdfG458ss= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=pass smtp.mailfrom=linux.intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=aHHppmGV; arc=none smtp.client-ip=198.175.65.16 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="aHHppmGV" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1761633896; x=1793169896; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=7R93AM51irQ+2d/T+qJcF1Qkq5IbJli4SD6al94qH0o=; b=aHHppmGVtFw1j/LHvW6AKDiC4vJlN83WPFQ9/oo7FY+IKZkwncBn0FCY L/xFMy/JHeeUaEmiYOkjYV53oKt7wZm61PjpuBuA/3hKcBQEVlN0c6Irb ZRsyMJ+N9eYogeumrJGD+S02dJ7kdUneTQwTRv+hs5CodbmjjkwX7zUFt iqEALR7t24pZ8BVajAIBMh5FWCwfPLwaWPyCJACSPw1WWZj1djuKAvcAv 6kbnHUJp0ssOaIqzgtoGpwJuX9cDfkbUhS/lmI/Tgovj+LLllOSt7x6IR nwXqnC7RRpFPCj+Zr/z3PRl/FsPr1Bkxr213t6ksM1mMUBlioHMnSZamZ Q==; X-CSE-ConnectionGUID: 4nMlwNUjT1iu+JFuLU6I7A== X-CSE-MsgGUID: a2Rxx/pWT165SLPm8GBcyA== X-IronPort-AV: E=McAfee;i="6800,10657,11586"; a="63876136" X-IronPort-AV: E=Sophos;i="6.19,260,1754982000"; d="scan'208";a="63876136" Received: from fmviesa003.fm.intel.com ([10.60.135.143]) by orvoesa108.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 27 Oct 2025 23:44:55 -0700 X-CSE-ConnectionGUID: Z+Al2gEkQS6Ii/zTaKOxqg== X-CSE-MsgGUID: zKGaDDSzT1eHFUdG72tb4g== X-ExtLoop1: 1 Received: from spr.sh.intel.com ([10.112.230.239]) by fmviesa003.fm.intel.com with ESMTP; 27 Oct 2025 23:44:51 -0700 From: Dapeng Mi To: Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , Namhyung Kim , Ian Rogers , Adrian Hunter , Alexander Shishkin , Andi Kleen , Eranian Stephane Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org, Dapeng Mi , Zide Chen , Falcon Thomas , Xudong Hao , Dapeng Mi , stable@vger.kernel.org Subject: [Patch v2] perf/x86/intel: Fix KASAN global-out-of-bounds warning Date: Tue, 28 Oct 2025 14:42:14 +0800 Message-Id: <20251028064214.1451968-1-dapeng1.mi@linux.intel.com> X-Mailer: git-send-email 2.34.1 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" When running "perf mem record" command on CWF, the below KASAN global-out-of-bounds warning is seen. 196.273657] =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D [ 196.273662] BUG: KASAN: global-out-of-bounds in cmt_latency_data+0x176/0= x1b0 [ 196.273669] Read of size 4 at addr ffffffffb721d000 by task dtlb/9850 [ 196.273676] CPU: 126 UID: 0 PID: 9850 Comm: dtlb Kdump: loaded Not taint= ed 6.17.0-rc3-2025-08-29-intel-next-34160-g316938187eb0 #1 PREEMPT(none) [ 196.273680] Hardware name: Intel Corporation AvenueCity/AvenueCity, BIOS= BHSDCRB1.IPC.3544.P83.2507110208 07/11/2025 [ 196.273682] Call Trace: [ 196.273683] [ 196.273684] dump_stack_lvl+0x55/0x70 [ 196.273689] print_address_description.constprop.0+0x2c/0x3d0 [ 196.273694] ? cmt_latency_data+0x176/0x1b0 [ 196.273696] print_report+0xb4/0x270 [ 196.273699] ? kasan_addr_to_slab+0xd/0xa0 [ 196.273702] kasan_report+0xb8/0xf0 [ 196.273705] ? cmt_latency_data+0x176/0x1b0 [ 196.273707] cmt_latency_data+0x176/0x1b0 [ 196.273710] setup_arch_pebs_sample_data+0xf49/0x2560 [ 196.273713] intel_pmu_drain_arch_pebs+0x577/0xb00 [ 196.273716] ? __pfx_intel_pmu_drain_arch_pebs+0x10/0x10 [ 196.273719] ? perf_output_begin+0x3e4/0xa10 [ 196.273724] ? intel_pmu_drain_bts_buffer+0xc2/0x6a0 [ 196.273727] ? __pfx_intel_pmu_drain_bts_buffer+0x10/0x10 [ 196.273730] handle_pmi_common+0x6c4/0xc80 [ 196.273734] ? __pfx_handle_pmi_common+0x10/0x10 [ 196.273738] ? intel_bts_interrupt+0xd3/0x4d0 [ 196.273740] ? __pfx_intel_bts_interrupt+0x10/0x10 [ 196.273742] ? intel_pmu_lbr_enable_all+0x25/0x150 [ 196.273745] intel_pmu_handle_irq+0x388/0x700 [ 196.273748] perf_event_nmi_handler+0xff/0x150 [ 196.273751] nmi_handle.part.0+0xa8/0x2d0 [ 196.273755] ? perf_output_begin+0x3e9/0xa10 [ 196.273757] default_do_nmi+0x79/0x1a0 [ 196.273760] fred_exc_nmi+0x40/0x90 [ 196.273762] asm_fred_entrypoint_kernel+0x45/0x60 [ 196.273765] RIP: 0010:perf_output_begin+0x3e9/0xa10 [ 196.273768] Code: 54 24 1c 85 d2 0f 85 19 03 00 00 48 8b 44 24 18 48 c1 = e8 03 42 0f b6 04 28 84 c0 74 08 3c 03 0f 8e 25 05 00 00 41 8b 44 24 18 e0 0c 48 98 48 83 e8 01 80 7c 24 2a 00 0f 85 f9 02 00 00 4c 29 [ 196.273770] RSP: 0018:ffffc9001cf575e8 EFLAGS: 00000246 [ 196.273774] RAX: 0000000000000080 RBX: ffff88c1a0f95028 RCX: 00000000000= 00004 [ 196.273775] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff88c08c8= f9408 [ 196.273777] RBP: 0000000000000028 R08: 0000000000000000 R09: ffffed18341= f2a05 [ 196.273778] R10: ffff88c1a0f9502f R11: ffff88c1a0dbe1b8 R12: ffff88c1a0f= 95000 [ 196.273779] R13: dffffc0000000000 R14: 0000000000000000 R15: ffffc9001cf= 577e0 [ 196.273782] 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 =3D=3D hybrid_big) So add is_hybrid() check before calling this WARN_ON_ONCE to fix the global-out-of-bounds access issue. Reported-by: Xudong Hao Cc: stable@vger.kernel.org Fixes: 090262439f66 ("perf/x86/intel: Rename model-specific pebs_latency_da= ta functions") Signed-off-by: Dapeng Mi Reviewed-by: Zide Chen --- Changes: v2: Wrap the line that exceeds 80 characters (Zide) arch/x86/events/intel/ds.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/arch/x86/events/intel/ds.c b/arch/x86/events/intel/ds.c index c0b7ac1c7594..01bc59e9286c 100644 --- a/arch/x86/events/intel/ds.c +++ b/arch/x86/events/intel/ds.c @@ -317,7 +317,8 @@ static u64 __grt_latency_data(struct perf_event *event,= u64 status, { u64 val; =20 - WARN_ON_ONCE(hybrid_pmu(event->pmu)->pmu_type =3D=3D hybrid_big); + WARN_ON_ONCE(is_hybrid() && + hybrid_pmu(event->pmu)->pmu_type =3D=3D hybrid_big); =20 dse &=3D PERF_PEBS_DATA_SOURCE_GRT_MASK; val =3D hybrid_var(event->pmu, pebs_data_source)[dse]; base-commit: 45e1dccc0653c50e377dae57ef086a8d0f71061d --=20 2.34.1