From: Stefan Hajnoczi <stefanha@redhat.com>
To: P J P <ppandit@redhat.com>
Cc: Qemu Developers <qemu-devel@nongnu.org>,
zhangboxian <zhangboxian@huawei.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Prasad J Pandit <pjp@fedoraproject.org>
Subject: Re: [Qemu-devel] [PATCH v1 2/2] tests: add test to check VirtQueue object
Date: Fri, 24 Nov 2017 11:49:20 +0000 [thread overview]
Message-ID: <20171124114920.GB12490@stefanha-x1.localdomain> (raw)
In-Reply-To: <20171124075542.16979-3-ppandit@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1550 bytes --]
On Fri, Nov 24, 2017 at 01:25:42PM +0530, P J P wrote:
> From: Prasad J Pandit <pjp@fedoraproject.org>
>
> An uninitialised VirtQueue object or one with Vring.align field
> set to zero(0) could lead to arithmetic exceptions. Add a unit
> test to validate it.
>
> Signed-off-by: Prasad J Pandit <pjp@fedoraproject.org>
> ---
> tests/virtio-blk-test.c | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/tests/virtio-blk-test.c b/tests/virtio-blk-test.c
> index e6fb9bac87..d00ceb0501 100644
> --- a/tests/virtio-blk-test.c
> +++ b/tests/virtio-blk-test.c
> @@ -674,6 +674,26 @@ static void pci_hotplug(void)
> qtest_shutdown(qs);
> }
>
> +static void test_vring_align(void)
It's important to include a doc comment so the purpose of the test is
clear:
/*
* Check that setting the vring addr on a non-existent virtqueue does
* not crash.
*/
I think the _align name is confusing since the vring alignment is not
directly affected by this test case. Please call it
test_nonexistent_virtqueue() instead.
> +{
> + QPCIBar bar0;
> + QOSState *qs;
> + QPCIDevice *dev;
> +
> + qs = pci_test_start();
> + dev = qpci_device_find(qs->pcibus, QPCI_DEVFN(4, 0));
> + g_assert(dev != NULL);
> +
> + qpci_device_enable(dev);
> + bar0 = qpci_iomap(dev, 0, NULL);
> +
> + qpci_io_writeb(dev, bar0, VIRTIO_PCI_QUEUE_SEL, 2);
> + qpci_io_writel(dev, bar0, VIRTIO_PCI_QUEUE_PFN, 1);
> +
> + g_free(dev);
> + qtest_shutdown(qs);
> +}
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2017-11-24 11:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-24 7:55 [Qemu-devel] [PATCH v1 0/2] check VirtiQueue Vring objects P J P
2017-11-24 7:55 ` [Qemu-devel] [PATCH v1 1/2] virtio: check VirtQueue Vring object is set P J P
2017-11-24 9:01 ` Cornelia Huck
2017-11-24 11:54 ` Stefan Hajnoczi
2017-11-24 7:55 ` [Qemu-devel] [PATCH v1 2/2] tests: add test to check VirtQueue object P J P
2017-11-24 11:49 ` Stefan Hajnoczi [this message]
2017-11-24 9:42 ` [Qemu-devel] [PATCH v1 0/2] check VirtiQueue Vring objects Paolo Bonzini
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=20171124114920.GB12490@stefanha-x1.localdomain \
--to=stefanha@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).