From: Dave Jiang <dave.jiang@intel.com>
To: Guixin Liu <kanie@linux.alibaba.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jic23@kernel.org>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Dan Williams <djbw@kernel.org>, Ira Weiny <iweiny@kernel.org>,
Li Ming <ming.li@zohomail.com>
Cc: linux-cxl@vger.kernel.org
Subject: Re: [PATCH v2] cxl/events: Test CME counter expiry with equality, not bitwise AND
Date: Tue, 22 Sep 2026 10:29:00 -0700 [thread overview]
Message-ID: <8908efc5-8add-4dcc-9df6-c4de9cf6de2b@intel.com> (raw)
In-Reply-To: <20260922082214.3526355-1-kanie@linux.alibaba.com>
On 9/22/26 1:22 AM, Guixin Liu wrote:
> 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>
> ---
> Found by code inspection during review of a downstream backport of
> these two patches. Reproduced in a QEMU CXL topology by injecting
> General Media events through the cxl-inject-general-media-event QMP
> command: a type 01h event warns in cxl_event_trace_record() without
> the fix and is traced without a warning with it; type 05h events that
> violate the spec conditions still warn.
>
> Changes since v1 [1]:
> - Collect the commit log suggested by Dave Jiang and the subject
> suggested by Alison Schofield.
> - Move the reproducer explanation below '---' (Dave Jiang).
> - Add the 'Assisted-by: LLM' tag (Dave Jiang).
>
> [1]: https://lore.kernel.org/all/20260921120932.1769566-1-kanie@linux.alibaba.com/
>
> drivers/cxl/core/mbox.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/cxl/core/mbox.c b/drivers/cxl/core/mbox.c
> index 55828a836c01..01341f524a93 100644
> --- a/drivers/cxl/core/mbox.c
> +++ b/drivers/cxl/core/mbox.c
> @@ -942,11 +942,11 @@ void cxl_event_trace_record(struct cxl_memdev *cxlmd,
>
> if (evt->gen_media.media_hdr.descriptor &
> CXL_GMER_EVT_DESC_THRESHOLD_EVENT)
> - WARN_ON_ONCE((evt->gen_media.media_hdr.type &
> + WARN_ON_ONCE((evt->gen_media.media_hdr.type ==
> CXL_GMER_MEM_EVT_TYPE_AP_CME_COUNTER_EXPIRE) &&
> !get_unaligned_le24(evt->gen_media.cme_count));
> else
> - WARN_ON_ONCE(evt->gen_media.media_hdr.type &
> + WARN_ON_ONCE(evt->gen_media.media_hdr.type ==
> CXL_GMER_MEM_EVT_TYPE_AP_CME_COUNTER_EXPIRE);
>
> trace_cxl_general_media(cxlmd, type, cxlr, hpa,
> @@ -957,11 +957,11 @@ void cxl_event_trace_record(struct cxl_memdev *cxlmd,
>
> if (evt->dram.media_hdr.descriptor &
> CXL_GMER_EVT_DESC_THRESHOLD_EVENT)
> - WARN_ON_ONCE((evt->dram.media_hdr.type &
> + WARN_ON_ONCE((evt->dram.media_hdr.type ==
> CXL_DER_MEM_EVT_TYPE_AP_CME_COUNTER_EXPIRE) &&
> !get_unaligned_le24(evt->dram.cvme_count));
> else
> - WARN_ON_ONCE(evt->dram.media_hdr.type &
> + WARN_ON_ONCE(evt->dram.media_hdr.type ==
> CXL_DER_MEM_EVT_TYPE_AP_CME_COUNTER_EXPIRE);
>
> trace_cxl_dram(cxlmd, type, cxlr, hpa, hpa_alias,
next prev parent reply other threads:[~2026-09-22 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 8:22 [PATCH v2] cxl/events: Test CME counter expiry with equality, not bitwise AND Guixin Liu
2026-09-22 17:29 ` Dave Jiang [this message]
2026-09-24 1:00 ` Jonathan Cameron
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8908efc5-8add-4dcc-9df6-c4de9cf6de2b@intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=dave@stgolabs.net \
--cc=djbw@kernel.org \
--cc=iweiny@kernel.org \
--cc=jic23@kernel.org \
--cc=kanie@linux.alibaba.com \
--cc=linux-cxl@vger.kernel.org \
--cc=ming.li@zohomail.com \
--cc=vishal.l.verma@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox