From: fan <nifan.cxl@gmail.com>
To: Ira Weiny <ira.weiny@intel.com>
Cc: Jonathan Cameron <jonathan.cameron@huawei.com>,
Fan Ni <nifan.cxl@gmail.com>, Dave Jiang <dave.jiang@intel.com>,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
Huai-Cheng Kuo <hchkuo@avery-design.com.tw>
Subject: Re: [PATCH v2 1/2] cxl/cdat: Handle cdat table build errors
Date: Tue, 19 Dec 2023 09:44:06 -0800 [thread overview]
Message-ID: <ZYHWZjsnQwcBEDpd@debian> (raw)
In-Reply-To: <20231117-fix-cdat-cs-v2-1-715399976d4d@intel.com>
On Wed, Nov 29, 2023 at 05:33:03PM -0800, Ira Weiny wrote:
> The callback for building CDAT tables may return negative error codes.
> This was previously unhandled and will result in potentially huge
> allocations later on in ct3_build_cdat()
>
> Detect the negative error code and defer cdat building.
>
> Fixes: f5ee7413d592 ("hw/mem/cxl-type3: Add CXL CDAT Data Object Exchange")
> Cc: Huai-Cheng Kuo <hchkuo@avery-design.com.tw>
> Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> Signed-off-by: Ira Weiny <ira.weiny@intel.com>
> ---
> hw/cxl/cxl-cdat.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/cxl/cxl-cdat.c b/hw/cxl/cxl-cdat.c
> index 639a2db3e17b..24829cf2428d 100644
> --- a/hw/cxl/cxl-cdat.c
> +++ b/hw/cxl/cxl-cdat.c
> @@ -63,7 +63,7 @@ static void ct3_build_cdat(CDATObject *cdat, Error **errp)
> cdat->built_buf_len = cdat->build_cdat_table(&cdat->built_buf,
> cdat->private);
>
> - if (!cdat->built_buf_len) {
> + if (cdat->built_buf_len <= 0) {
> /* Build later as not all data available yet */
> cdat->to_update = true;
> return;
>
The fix looks good to me. Just curious how to really build cdat table
again when an error occurs, for example, the memory allocation fails.
Fan
> --
> 2.42.0
>
next prev parent reply other threads:[~2023-12-19 17:44 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 [this message]
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 ` [PATCH v2 2/2] cxl/cdat: Fix header sum value in CDAT checksum Ira Weiny
2023-11-30 16:20 ` 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=ZYHWZjsnQwcBEDpd@debian \
--to=nifan.cxl@gmail.com \
--cc=dave.jiang@intel.com \
--cc=hchkuo@avery-design.com.tw \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.