From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Michael Tsirkin <mst@redhat.com>, <qemu-devel@nongnu.org>,
"Vinayak Holikatti" <vinayak.kh@samsung.com>,
<linuxarm@huawei.com>, <linux-cxl@vger.kernel.org>,
Ravi Shankar <venkataravis@micron.com>,
qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PATCH qemu 0/2] hw/cxl: Two media operations related fixes.
Date: Fri, 6 Feb 2026 09:42:39 +0000 [thread overview]
Message-ID: <20260206094239.000065c4@huawei.com> (raw)
In-Reply-To: <3e767269-b39c-42e2-8283-598e16aa7b71@tls.msk.ru>
On Fri, 6 Feb 2026 01:11:55 +0300
Michael Tokarev <mjt@tls.msk.ru> wrote:
> On 1/2/26 18:47, Jonathan Cameron via wrote:
> > Peter reported both of these last cycle. Both are related to sanity
> > checking parameters.
> >
> > Jonathan Cameron (2):
> > hw/cxl: Check for overflow on santize media as both base and offset
> > 64bit.
> > hw/cxl: Take into account how many media operations are requested for
> > param check
> >
> > hw/cxl/cxl-mailbox-utils.c | 11 ++++++++---
> > 1 file changed, 8 insertions(+), 3 deletions(-)
>
> Is this one worth picking up for qemu-stable (10.1.x & 10.2.x)?
>
They are fairly obscure features but if it applies cleanly it seems
sensible to backport.
Thanks
Jonathan
> Thanks,
>
> /mjt
prev parent reply other threads:[~2026-02-06 9:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-02 15:47 [PATCH qemu 0/2] hw/cxl: Two media operations related fixes Jonathan Cameron
2026-01-02 15:47 ` [PATCH qemu 1/2] hw/cxl: Check for overflow on santize media as both base and offset 64bit Jonathan Cameron
2026-01-02 15:47 ` [PATCH qemu 2/2] hw/cxl: Take into account how many media operations are requested for param check Jonathan Cameron
2026-02-04 11:15 ` [PATCH qemu 0/2] hw/cxl: Two media operations related fixes Jonathan Cameron
2026-02-05 22:11 ` Michael Tokarev
2026-02-06 9:42 ` Jonathan Cameron [this message]
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=20260206094239.000065c4@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mjt@tls.msk.ru \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=venkataravis@micron.com \
--cc=vinayak.kh@samsung.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