From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: <shiju.jose@huawei.com>
Cc: <qemu-devel@nongnu.org>, <linux-cxl@vger.kernel.org>,
<mst@redhat.com>, <peter.maydell@linaro.org>, <dave@stgolabs.net>,
<linuxarm@huawei.com>
Subject: Re: [PATCH v2 0/3] hw/cxl: Add fixes in maintenance, PPR and event records
Date: Tue, 17 Mar 2026 16:45:56 +0000 [thread overview]
Message-ID: <20260317164556.0000794d@huawei.com> (raw)
In-Reply-To: <20260306101423.986-1-shiju.jose@huawei.com>
On Fri, 6 Mar 2026 10:14:19 +0000
<shiju.jose@huawei.com> wrote:
> From: Shiju Jose <shiju.jose@huawei.com>
>
> Add few fixes in CXL maintenance, PPR and event records generation.
All 3 of these look good to me.
Michael, please pick these up directly (assuming you think
they look good as well1)
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>
Thanks,
Jonathan
>
> 1. In cxl_create_mem_sparing_event_records(), replace strncpy with memcpy
> to solve coverity warning (CID 1645325) to copy the entire component ID
> data, which is 16 bytes data, not a string.
>
> 2. In cxl_maintenance_insert(),
> - replace strncpy with memcpy to copy full data because component ID is
> 16 bytes data, not a string.
> - remove memset which is not required.
>
> 3. In cxl_perform_ppr(), remove and free the maintenance entry from QLIST
> if match is found and PPR operation is performed.
>
> 4. Component ID in CXL events is 16 bytes data, not a string, but event
> record generation copy 15 bytes only from the qmp "component-id" field
> using strncpy. Replace strncpy with memcpy and copy the entire component
> ID data.
>
> Changes:
> v1 -> v2
> 1. Fix for the feedback from Jonathan.
> - Modified title of patch[1] & patch[3].
> - Added fixes tags to all 3 patche's header.
>
> Shiju Jose (3):
> hw/cxl: Fix handling of component ID to not assume it is a string
> hw/cxl: Add fixes in Post Package Repair (PPR)
> hw/cxl/events: Fix handling of component ID in event records
> generation to not assume it is a string
>
> hw/cxl/cxl-mailbox-utils.c | 6 ++++--
> hw/mem/cxl_type3.c | 13 ++++---------
> 2 files changed, 8 insertions(+), 11 deletions(-)
>
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron via qemu development <qemu-devel@nongnu.org>
To: <shiju.jose@huawei.com>
Cc: <qemu-devel@nongnu.org>, <linux-cxl@vger.kernel.org>,
<mst@redhat.com>, <peter.maydell@linaro.org>, <dave@stgolabs.net>,
<linuxarm@huawei.com>
Subject: Re: [PATCH v2 0/3] hw/cxl: Add fixes in maintenance, PPR and event records
Date: Tue, 17 Mar 2026 16:45:56 +0000 [thread overview]
Message-ID: <20260317164556.0000794d@huawei.com> (raw)
In-Reply-To: <20260306101423.986-1-shiju.jose@huawei.com>
On Fri, 6 Mar 2026 10:14:19 +0000
<shiju.jose@huawei.com> wrote:
> From: Shiju Jose <shiju.jose@huawei.com>
>
> Add few fixes in CXL maintenance, PPR and event records generation.
All 3 of these look good to me.
Michael, please pick these up directly (assuming you think
they look good as well1)
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>
Thanks,
Jonathan
>
> 1. In cxl_create_mem_sparing_event_records(), replace strncpy with memcpy
> to solve coverity warning (CID 1645325) to copy the entire component ID
> data, which is 16 bytes data, not a string.
>
> 2. In cxl_maintenance_insert(),
> - replace strncpy with memcpy to copy full data because component ID is
> 16 bytes data, not a string.
> - remove memset which is not required.
>
> 3. In cxl_perform_ppr(), remove and free the maintenance entry from QLIST
> if match is found and PPR operation is performed.
>
> 4. Component ID in CXL events is 16 bytes data, not a string, but event
> record generation copy 15 bytes only from the qmp "component-id" field
> using strncpy. Replace strncpy with memcpy and copy the entire component
> ID data.
>
> Changes:
> v1 -> v2
> 1. Fix for the feedback from Jonathan.
> - Modified title of patch[1] & patch[3].
> - Added fixes tags to all 3 patche's header.
>
> Shiju Jose (3):
> hw/cxl: Fix handling of component ID to not assume it is a string
> hw/cxl: Add fixes in Post Package Repair (PPR)
> hw/cxl/events: Fix handling of component ID in event records
> generation to not assume it is a string
>
> hw/cxl/cxl-mailbox-utils.c | 6 ++++--
> hw/mem/cxl_type3.c | 13 ++++---------
> 2 files changed, 8 insertions(+), 11 deletions(-)
>
next prev parent reply other threads:[~2026-03-17 16:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 10:14 [PATCH v2 0/3] hw/cxl: Add fixes in maintenance, PPR and event records shiju.jose
2026-03-06 10:14 ` shiju.jose--- via qemu development
2026-03-06 10:14 ` [PATCH v2 1/3] hw/cxl: Fix handling of component ID to not assume it is a string shiju.jose
2026-03-06 10:14 ` shiju.jose--- via qemu development
2026-03-06 10:14 ` [PATCH v2 2/3] hw/cxl: Add fixes in Post Package Repair (PPR) shiju.jose
2026-03-06 10:14 ` shiju.jose--- via qemu development
2026-03-06 10:14 ` [PATCH v2 3/3] hw/cxl/events: Fix handling of component ID in event records generation to not assume it is a string shiju.jose
2026-03-06 10:14 ` shiju.jose--- via qemu development
2026-03-17 16:45 ` Jonathan Cameron [this message]
2026-03-17 16:45 ` [PATCH v2 0/3] hw/cxl: Add fixes in maintenance, PPR and event records Jonathan Cameron via qemu development
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=20260317164556.0000794d@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=dave@stgolabs.net \
--cc=linux-cxl@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=shiju.jose@huawei.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 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.