From: zhenwei pi <zhenwei.pi@linux.dev>
To: qemu-devel@nongnu.org
Cc: mst@redhat.com, arei.gonglei@huawei.com,
nakamurajames123@gmail.com, qemu-security@nongnu.org,
mcascell@redhat.com, zhenwei pi <zhenwei.pi@linux.dev>
Subject: [PATCH 0/2] Avoid QEMU OOM on huge request from guest
Date: Sun, 14 Dec 2025 17:09:37 +0800 [thread overview]
Message-ID: <20251214090939.408436-1-zhenwei.pi@linux.dev> (raw)
Fix two issues in this series:
- Verify asym request size from device level
- Limit the maximum size for cryptodev builtin driver
zhenwei pi (2):
hw/virtio/virtio-crypto: verify asym request size
cryptodev-builtin: Limit the maximum size
backends/cryptodev-builtin.c | 9 +++------
hw/virtio/virtio-crypto.c | 7 +++++++
2 files changed, 10 insertions(+), 6 deletions(-)
--
2.43.0
next reply other threads:[~2025-12-14 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-14 9:09 zhenwei pi [this message]
2025-12-14 9:09 ` [PATCH 1/2] hw/virtio/virtio-crypto: verify asym request size zhenwei pi
2025-12-14 9:09 ` [PATCH 2/2] cryptodev-builtin: Limit the maximum size zhenwei pi
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=20251214090939.408436-1-zhenwei.pi@linux.dev \
--to=zhenwei.pi@linux.dev \
--cc=arei.gonglei@huawei.com \
--cc=mcascell@redhat.com \
--cc=mst@redhat.com \
--cc=nakamurajames123@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-security@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;
as well as URLs for NNTP newsgroup(s).