From: Dave Jiang <dave.jiang@intel.com>
To: Alison Schofield <alison.schofield@intel.com>
Cc: linux-cxl@vger.kernel.org, dave@stgolabs.net,
jonathan.cameron@huawei.com, vishal.l.verma@intel.com,
ira.weiny@intel.com, dan.j.williams@intel.com
Subject: Re: [PATCH 4/4] cxl: Adjust offset calculation for poison injection
Date: Fri, 31 Oct 2025 14:06:04 -0700 [thread overview]
Message-ID: <770c29cc-628b-496f-bfb6-6e64b10336c1@intel.com> (raw)
In-Reply-To: <aQUi5Tbcn2IHNgzY@aschofie-mobl2.lan>
On 10/31/25 1:58 PM, Alison Schofield wrote:
> On Fri, Oct 31, 2025 at 10:32:24AM -0700, Dave Jiang wrote:
>> The HPA to DPA translation for poison injection assumes that the
>> base address starts from where the CXL region begins. When the
>> extended linear cache is active, the offset can be within the DRAM
>> region. Adjust the offset so that it correctly reflects the offset
>> within the CXL region.
>
> Dave, good catch!
>
> This breakage was added in 6.18-rc1. Please consider it for a pull
> request before the end of 6.18.
>
> Here's justification and Fixes Tag:
>
> Without this patch, when a user intends to inject poison at an offset
> in region, it can inject poison into a location in a device that is
> not mapped by that region.
>
> The test case in cxl-poison-elc.sh that exposed this issue, injected
> poison 0x20000000 which should have been the first byte of the CXL
> half of an Extended Linear Cache (ELC) region. Instead, it injected
> poison at the next byte of a device beyond the regions mapping.
>
> Fixes: c3dd67681c70 ("cxl/region: Add inject and clear poison by region offset")
>
> Reviewed-by: Alison Schofield <alison.schofield@intel.com>
>
Yeah I can move it to fixes instead
next prev parent reply other threads:[~2025-10-31 21:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 17:32 [PATCH 0/4] cxl/test: Add unit testing for extended linear cache Dave Jiang
2025-10-31 17:32 ` [PATCH 1/4] cxl/test: Standardize CXL auto region size Dave Jiang
2025-11-11 14:08 ` Jonathan Cameron
2025-11-15 2:59 ` Alison Schofield
2025-10-31 17:32 ` [PATCH 2/4] cxl/test: Add cxl_test CFMWS support for extended linear cache Dave Jiang
2025-11-11 14:09 ` Jonathan Cameron
2025-11-15 3:00 ` Alison Schofield
2025-10-31 17:32 ` [PATCH 3/4] cxl/test: Add support for acpi " Dave Jiang
2025-11-11 14:13 ` Jonathan Cameron
2025-11-15 3:01 ` Alison Schofield
2025-10-31 17:32 ` [PATCH 4/4] cxl: Adjust offset calculation for poison injection Dave Jiang
2025-10-31 20:58 ` Alison Schofield
2025-10-31 21:06 ` Dave Jiang [this message]
2025-11-07 17:52 ` Dave Jiang
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=770c29cc-628b-496f-bfb6-6e64b10336c1@intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--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