From: Jia Jia <physicalmtea@gmail.com>
To: qemu-devel@nongnu.org
Cc: Jonathan Cameron <jic23@kernel.org>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Fan Ni <fan.ni@samsung.com>, Fabiano Rosas <farosas@suse.de>,
Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
linux-cxl@vger.kernel.org
Subject: [PATCH v3 0/2] hw/cxl: bound Set Feature writes
Date: Thu, 28 May 2026 13:55:23 +0800 [thread overview]
Message-ID: <cover.1779946245.git.physicalmtea@gmail.com> (raw)
In-Reply-To: <20260429152750.2409174-1-physicalmtea@gmail.com>
Hi Jonathan,
Thanks for the review.
This v3 splits the helper extraction from the actual bug fix. Patch 1
is a refactor only: it folds the existing patrol scrub and ECS bounds
checks into a helper, with no intended functional change.
Patch 2 uses that helper for the remaining Set Feature branches that
still copy into fixed-size write-attribute buffers without bounds
validation. That patch carries the Fixes tags.
I have left the qtest out of this backportable bugfix series for now.
I can send it separately after addressing the x86-only and magic-value
comments.
Changes since v2:
- split helper extraction from the bug fix
- add Fixes tags to the bug-fixing patch
- leave the qtest for a separate follow-up
Jia Jia (2):
hw/cxl: factor Set Feature write bounds helper
hw/cxl: validate PPR and sparing Set Feature writes
hw/cxl/cxl-mailbox-utils.c | 94 ++++++++++++++++++++++++++++----------
1 file changed, 70 insertions(+), 24 deletions(-)
--
2.34.1
next prev parent reply other threads:[~2026-05-28 5:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFEAcA_DnrvSCVY3f2q=3OnXt0+708BcwSJ=KhMn1t3sbbXQbg@mail.gmail.com>
2026-04-29 15:27 ` [PATCH v2] hw/cxl: bound Set Feature writes Jia Jia
2026-05-18 16:50 ` Jonathan Cameron
2026-05-28 5:55 ` Jia Jia [this message]
2026-05-28 5:55 ` [PATCH v3 1/2] hw/cxl: factor Set Feature write bounds helper Jia Jia
2026-05-28 5:55 ` [PATCH v3 2/2] hw/cxl: validate PPR and sparing Set Feature writes Jia Jia
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=cover.1779946245.git.physicalmtea@gmail.com \
--to=physicalmtea@gmail.com \
--cc=fan.ni@samsung.com \
--cc=farosas@suse.de \
--cc=jic23@kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox