From: Ira Weiny <ira.weiny@intel.com>
To: Jonathan Cameron <jonathan.cameron@huawei.com>,
Fan Ni <nifan.cxl@gmail.com>
Cc: Dave Jiang <dave.jiang@intel.com>,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
Ira Weiny <ira.weiny@intel.com>,
Huai-Cheng Kuo <hchkuo@avery-design.com.tw>
Subject: [PATCH v2 2/2] cxl/cdat: Fix header sum value in CDAT checksum
Date: Wed, 29 Nov 2023 17:33:04 -0800 [thread overview]
Message-ID: <20231117-fix-cdat-cs-v2-2-715399976d4d@intel.com> (raw)
In-Reply-To: <20231117-fix-cdat-cs-v2-0-715399976d4d@intel.com>
The addition of the DCD support for CXL type-3 devices extended the CDAT
table large enough that the checksum being returned was incorrect.[1]
This was because the checksum value was using the header length field
rather than each of the 4 bytes of the length field. This was
previously not seen because the length of the CDAT data was less than
256 thus resulting in an equivalent checksum value.
Properly calculate the checksum for the CDAT header.
[1] https://lore.kernel.org/all/20231116-fix-cdat-devm-free-v1-1-b148b40707d7@intel.com/
Fixes: aba578bdace5 ("hw/cxl/cdat: CXL CDAT Data Object Exchange implementation")
Cc: Huai-Cheng Kuo <hchkuo@avery-design.com.tw>
Signed-off-by: Ira Weiny <ira.weiny@intel.com>
---
Changes from V1:
[djiang: Remove do {} while (0);]
---
hw/cxl/cxl-cdat.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/hw/cxl/cxl-cdat.c b/hw/cxl/cxl-cdat.c
index 24829cf2428d..67e44a4f992a 100644
--- a/hw/cxl/cxl-cdat.c
+++ b/hw/cxl/cxl-cdat.c
@@ -49,6 +49,7 @@ static void ct3_build_cdat(CDATObject *cdat, Error **errp)
g_autofree CDATTableHeader *cdat_header = NULL;
g_autofree CDATEntry *cdat_st = NULL;
uint8_t sum = 0;
+ uint8_t *buf;
int ent, i;
/* Use default table if fopen == NULL */
@@ -95,8 +96,12 @@ static void ct3_build_cdat(CDATObject *cdat, Error **errp)
/* For now, no runtime updates */
cdat_header->sequence = 0;
cdat_header->length += sizeof(CDATTableHeader);
- sum += cdat_header->revision + cdat_header->sequence +
- cdat_header->length;
+
+ buf = (uint8_t *)cdat_header;
+ for (i = 0; i < sizeof(*cdat_header); i++) {
+ sum += buf[i];
+ }
+
/* Sum of all bytes including checksum must be 0 */
cdat_header->checksum = ~sum + 1;
--
2.42.0
next prev parent reply other threads:[~2023-11-30 1:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 1:33 [PATCH v2 0/2] cxl/cdat: Fixes for CXL CDAT processing Ira Weiny
2023-11-30 1:33 ` [PATCH v2 1/2] cxl/cdat: Handle cdat table build errors Ira Weiny
2023-12-19 17:44 ` fan
2023-12-20 19:55 ` Ira Weiny
2024-01-08 15:03 ` Jonathan Cameron
2024-01-08 16:06 ` Ira Weiny
2024-01-08 18:00 ` Jonathan Cameron
2024-01-08 18:05 ` Jonathan Cameron
2024-01-09 2:48 ` Ira Weiny
2024-01-09 15:34 ` Jonathan Cameron
2023-11-30 1:33 ` Ira Weiny [this message]
2023-11-30 16:20 ` [PATCH v2 2/2] cxl/cdat: Fix header sum value in CDAT checksum Dave Jiang
2023-12-18 12:33 ` Jonathan Cameron
2023-12-18 23:14 ` Ira Weiny
2023-12-18 23:30 ` Dan Williams
2023-12-19 16:58 ` Jonathan Cameron
2023-12-21 0:22 ` Dan Williams
2023-12-18 13:28 ` Jonathan Cameron
2023-12-19 23:32 ` Ira Weiny
2024-01-08 15:09 ` Jonathan Cameron
2023-12-19 17:52 ` fan
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=20231117-fix-cdat-cs-v2-2-715399976d4d@intel.com \
--to=ira.weiny@intel.com \
--cc=dave.jiang@intel.com \
--cc=hchkuo@avery-design.com.tw \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nifan.cxl@gmail.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