From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: kvm-devel <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>,
lf-virt <virtualization@lists.linux-foundation.org>,
Anthony Liguori <aliguori@linux.vnet.ibm.com>,
target-devel <target-devel@vger.kernel.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH-v2 0/3] virtio/vhost: Add checks for uninitialized VQs
Date: Tue, 02 Apr 2013 16:16:54 -0700 [thread overview]
Message-ID: <1364944614.3898.202.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <20130402120145.GB21545@redhat.com>
On Tue, 2013-04-02 at 15:01 +0300, Michael S. Tsirkin wrote:
> On Mon, Apr 01, 2013 at 11:58:21PM +0000, Nicholas A. Bellinger wrote:
> > From: Nicholas Bellinger <nab@linux-iscsi.org>
> >
> > Hi folks,
> >
> > This series adds a virtio_queue_valid() for use by virtio-pci code in
> > order to prevent opreations upon uninitialized VQs, which is currently
> > expected to occur during seabios setup of virtio-scsi with in-flight
> > vhost-scsi-pci device code.
> >
> > On the vhost side, it also adds virtio_queue_valid() sanity checks in
> > vhost_virtqueue_[start,stop]() and vhost_verify_ring_mappings() in order
> > to skip the same uninitialized VQs.
> >
> > Changes from v1:
> > - Remove now unnecessary virtio_queue_get_num() calls in virtio-pci.c
> > - Add virtio_queue_valid() calls in vhost_virtqueue_[start,stop]()
> >
> > Please review.
> >
> > --nab
>
> Looks reasonable.
> Acked-by: Michael S. Tsirkin <mst@redhat.com>
>
Thanks MST!
Anthony, do you want to pick these up now..? Or shall I include in the
next vhost-scsi-pci PATCH-v3 series..?
--nab
> So - does this fix the issues you saw with vhost-scsi?
>
> > Michael S. Tsirkin (1):
> > virtio: add API to check that ring is setup
> >
> > Nicholas Bellinger (2):
> > virtio-pci: Add virtio_queue_valid checks ahead of
> > virtio_queue_get_num
> > vhost: Skip uninitialized VQs in vhost_virtqueue_[start,stop]
> >
> > hw/vhost.c | 12 ++++++++++++
> > hw/virtio-pci.c | 34 +++++++++++++++-------------------
> > hw/virtio.c | 5 +++++
> > hw/virtio.h | 1 +
> > 4 files changed, 33 insertions(+), 19 deletions(-)
> >
> > --
> > 1.7.2.5
> --
> To unsubscribe from this list: send the line "unsubscribe target-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-04-02 23:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 23:58 [PATCH-v2 0/3] virtio/vhost: Add checks for uninitialized VQs Nicholas A. Bellinger
2013-04-01 23:58 ` [PATCH-v2 1/3] virtio: add API to check that ring is setup Nicholas A. Bellinger
2013-04-01 23:58 ` [PATCH-v2 2/3] virtio-pci: Add virtio_queue_valid checks ahead of virtio_queue_get_num Nicholas A. Bellinger
2013-04-01 23:58 ` [PATCH-v2 3/3] vhost: Skip uninitialized VQs in vhost_virtqueue_[start,stop] Nicholas A. Bellinger
2013-04-02 12:01 ` [PATCH-v2 0/3] virtio/vhost: Add checks for uninitialized VQs Michael S. Tsirkin
2013-04-02 23:16 ` Nicholas A. Bellinger [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=1364944614.3898.202.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=aliguori@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=target-devel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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