From: Stefan Hajnoczi <stefanha@redhat.com>
To: Dongli Zhang <dongli.zhang@oracle.com>
Cc: virtualization@lists.linux.dev, mst@redhat.com,
jasowangio@gmail.com, michael.christie@oracle.com,
pbonzini@redhat.com, eperezma@redhat.com, kvm@vger.kernel.org,
joe.jin@oracle.com
Subject: Re: [PATCH v2 0/2] vhost-scsi: fix max_io_vqs handling
Date: Tue, 11 Aug 2026 09:51:27 -0400 [thread overview]
Message-ID: <20260811135127.GB111558@fedora> (raw)
In-Reply-To: <20260802172534.260047-1-dongli.zhang@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
On Sun, Aug 02, 2026 at 10:24:54AM -0700, Dongli Zhang wrote:
> Avoid high-order kmalloc() allocations for the vhost-scsi virtqueue array,
> and clamp out-of-range max_io_vqs updates so the stored value remains
> within the supported range.
>
> v1->v2:
> - Access vhost_scsi_max_io_vqs with READ_ONCE().
> - Clamp out-of-range max_io_vqs values instead of rejecting them.
>
> Dongli Zhang (2):
> vhost-scsi: use kvzalloc for vq array allocation
> vhost-scsi: vhost-scsi: clamp max_io_vqs module parameter
>
> drivers/vhost/scsi.c | 49 ++++++++++++++++++++++++++++++++++-------------
> 1 file changed, 36 insertions(+), 13 deletions(-)
>
> base-commit: 2d2338c93da79b3bfe4b6099a931d9468d539952
>
> Thank you very much!
>
> Dongli Zhang
>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-08-11 13:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-02 17:24 [PATCH v2 0/2] vhost-scsi: fix max_io_vqs handling Dongli Zhang
2026-08-02 17:24 ` [PATCH v2 1/2] vhost-scsi: use kvzalloc for vq array allocation Dongli Zhang
2026-08-06 18:30 ` Mike Christie
2026-08-02 17:24 ` [PATCH v2 2/2] vhost-scsi: clamp max_io_vqs module parameter Dongli Zhang
2026-08-06 19:30 ` Mike Christie
2026-08-11 13:51 ` Stefan Hajnoczi [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=20260811135127.GB111558@fedora \
--to=stefanha@redhat.com \
--cc=dongli.zhang@oracle.com \
--cc=eperezma@redhat.com \
--cc=jasowangio@gmail.com \
--cc=joe.jin@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=michael.christie@oracle.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=virtualization@lists.linux.dev \
/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.