diff options
| author | Guixin Liu <kanie@linux.alibaba.com> | 2026-09-22 16:22:14 +0800 |
|---|---|---|
| committer | Dave Jiang <dave.jiang@intel.com> | 2026-10-15 08:13:17 -0700 |
| commit | b94ba9a1f2d5c57f2eec67d502bb8fdd1e53c87a (patch) | |
| tree | b421e1a59da59b9afa5505445d095998292109b7 /scripts/basic/split-include.c | |
| parent | 2658c66a5efb5f30f5ced708a5de831845b43f6d (diff) | |
| download | linux-next-b94ba9a1f2d5c57f2eec67d502bb8fdd1e53c87a.tar.gz linux-next-b94ba9a1f2d5c57f2eec67d502bb8fdd1e53c87a.zip | |
cxl/events: Test CME counter expiry with equality, not bitwise AND
The Memory Event Type field in the General Media and DRAM event records
is an enumeration, not a bitmask. The validity checks for the advanced
programmable CME counter expiration event (05h) test the field with a
bitwise AND, so types 01h, 03h, 04h and 06h match it as well.
A device reporting one of those types trips WARN_ON_ONCE once the
general media or DRAM tracepoint is enabled, which is the case anywhere
rasdaemon collects CXL events. Under panic_on_warn=1 that kills the
machine.
Compare the type field for equality instead. Type 05h records that do
violate the spec conditions still warn.
Fixes: cd3b36cfc659 ("cxl/events: Add extra validity checks for corrected memory error count in General Media Event Record")
Fixes: d8145bb8af5c ("cxl/events: Add extra validity checks for CVME count in DRAM Event Record")
Cc: stable@vger.kernel.org
Assisted-by: LLM
Signed-off-by: Guixin Liu <kanie@linux.alibaba.com>
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
Reviewed-by: Jonathan Cameron <jonathan.cameron@oss.qualcomm.com>
Link: https://patch.msgid.link/20260922082214.3526355-1-kanie@linux.alibaba.com
Signed-off-by: Dave Jiang <dave.jiang@intel.com>
Diffstat (limited to 'scripts/basic/split-include.c')
0 files changed, 0 insertions, 0 deletions
