From: Stefan Hajnoczi <stefanha@redhat.com>
To: P J P <ppandit@redhat.com>
Cc: Qemu Developers <qemu-devel@nongnu.org>,
Cornelia Huck <cohuck@redhat.com>,
zhangboxian <zhangboxian@huawei.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Prasad J Pandit <pjp@fedoraproject.org>
Subject: Re: [Qemu-devel] [PATCH v4 0/2] check VirtiQueue Vring objects
Date: Thu, 30 Nov 2017 14:53:27 +0000 [thread overview]
Message-ID: <20171130145327.GA15942@stefanha-x1.localdomain> (raw)
In-Reply-To: <20171129174428.27548-1-ppandit@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 733 bytes --]
On Wed, Nov 29, 2017 at 11:14:26PM +0530, P J P wrote:
> From: Prasad J Pandit <pjp@fedoraproject.org>
>
> Hello,
>
> A guest could attempt to use an uninitialised VirtQueue object
> or set Vring object with undue values, raising an unexpected
> exception in Qemu. This patch set fixes this issue and also adds
> a unit test to the suite.
>
> Thank you.
> --
> Prasad J Pandit (2):
> virtio: check VirtQueue Vring object is set
> tests: add test to check VirtQueue object
>
> hw/virtio/virtio.c | 14 +++++++++++---
> tests/virtio-blk-test.c | 25 +++++++++++++++++++++++++
> 2 files changed, 36 insertions(+), 3 deletions(-)
>
> --
> 2.13.6
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2017-11-30 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 17:44 [Qemu-devel] [PATCH v4 0/2] check VirtiQueue Vring objects P J P
2017-11-29 17:44 ` [Qemu-devel] [PATCH v4 1/2] virtio: check VirtQueue Vring object is set P J P
2017-11-30 9:32 ` Cornelia Huck
2017-11-29 17:44 ` [Qemu-devel] [PATCH v4 2/2] tests: add test to check VirtQueue object P J P
2017-11-30 14:53 ` Stefan Hajnoczi [this message]
2017-11-30 14:54 ` [Qemu-devel] [PATCH v4 0/2] check VirtiQueue Vring objects Stefan Hajnoczi
2017-11-30 18:11 ` P J P
2017-12-07 7:07 ` P J P
2017-12-07 17:53 ` Michael S. Tsirkin
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=20171130145327.GA15942@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=cohuck@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pjp@fedoraproject.org \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhangboxian@huawei.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;
as well as URLs for NNTP newsgroup(s).