From: Platform Team regression test user <citrix-osstest@xenproject.org>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [qemu-upstream-4.4-testing baseline-only test] 66857: regressions - trouble: broken/fail/pass
Date: Fri, 29 Jul 2016 10:44:16 +0100 [thread overview]
Message-ID: <osstest-66857-mainreport@xen.org> (raw)
This run is configured for baseline tests only.
flight 66857 qemu-upstream-4.4-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/66857/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-multivcpu 3 host-install(3) broken REGR. vs. 66488
test-amd64-i386-pv 3 host-install(3) broken REGR. vs. 66488
test-amd64-amd64-xl-qemuu-debianhvm-amd64 3 host-install(3) broken REGR. vs. 66488
test-amd64-amd64-xl-qemuu-winxpsp3 3 host-install(3) broken REGR. vs. 66488
test-amd64-amd64-libvirt 3 host-install(3) broken REGR. vs. 66488
test-amd64-amd64-xl-qemuu-win7-amd64 3 host-install(3) broken REGR. vs. 66488
test-amd64-i386-libvirt-pair 4 host-install/dst_host(4) broken REGR. vs. 66488
test-amd64-i386-pair 4 host-install/dst_host(4) broken REGR. vs. 66488
test-amd64-amd64-pair 3 host-install/src_host(3) broken REGR. vs. 66488
test-amd64-amd64-libvirt-pair 3 host-install/src_host(3) broken REGR. vs. 66488
test-amd64-i386-xl-qemuu-win7-amd64 15 guest-localmigrate/x10 fail REGR. vs. 66488
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-pv 17 guest-localmigrate/x10 fail like 66488
test-amd64-amd64-xl-qcow2 21 leak-check/check fail like 66488
Tests which did not succeed, but are not blocking:
test-amd64-amd64-qemuu-nested-intel 16 debian-hvm-install/l1/l2 fail never pass
test-amd64-amd64-qemuu-nested-amd 16 debian-hvm-install/l1/l2 fail never pass
test-amd64-i386-libvirt 12 migrate-support-check fail never pass
test-amd64-amd64-libvirt-vhd 11 migrate-support-check fail never pass
version targeted for testing:
qemuu e72488cdcf2208f2df334fa88c35b33e695fa93b
baseline version:
qemuu ca3d95113903ccffe52af3922bbf7bd14a9acc78
Last test of basis 66488 2016-07-01 10:51:34 Z 27 days
Testing same since 66857 2016-07-29 04:46:53 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
P J P <ppandit@redhat.com>
Stefan Hajnoczi <stefanha@redhat.com>
Stefano Stabellini <sstabellini@kernel.org>
jobs:
build-amd64-xend pass
build-i386-xend pass
build-amd64 pass
build-i386 pass
build-amd64-libvirt pass
build-i386-libvirt pass
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl pass
test-amd64-i386-xl pass
test-amd64-amd64-qemuu-nested-amd fail
test-amd64-i386-qemuu-rhel6hvm-amd pass
test-amd64-amd64-xl-qemuu-debianhvm-amd64 broken
test-amd64-i386-xl-qemuu-debianhvm-amd64 pass
test-amd64-i386-freebsd10-amd64 pass
test-amd64-amd64-xl-qemuu-ovmf-amd64 pass
test-amd64-i386-xl-qemuu-ovmf-amd64 pass
test-amd64-amd64-xl-qemuu-win7-amd64 broken
test-amd64-i386-xl-qemuu-win7-amd64 fail
test-amd64-amd64-xl-credit2 pass
test-amd64-i386-freebsd10-i386 pass
test-amd64-amd64-qemuu-nested-intel fail
test-amd64-i386-qemuu-rhel6hvm-intel pass
test-amd64-amd64-libvirt broken
test-amd64-i386-libvirt pass
test-amd64-amd64-xl-multivcpu broken
test-amd64-amd64-pair broken
test-amd64-i386-pair broken
test-amd64-amd64-libvirt-pair broken
test-amd64-i386-libvirt-pair broken
test-amd64-amd64-pv fail
test-amd64-i386-pv broken
test-amd64-amd64-amd64-pvgrub pass
test-amd64-amd64-i386-pvgrub pass
test-amd64-amd64-pygrub pass
test-amd64-amd64-xl-qcow2 fail
test-amd64-i386-xl-raw pass
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 pass
test-amd64-amd64-libvirt-vhd pass
test-amd64-amd64-xl-qemuu-winxpsp3 broken
------------------------------------------------------------
sg-report-flight on osstest.xs.citrite.net
logs: /home/osstest/logs
images: /home/osstest/images
Logs, config files, etc. are available at
http://osstest.xs.citrite.net/~osstest/testlogs/logs
Test harness code can be found at
http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary
broken-step test-amd64-amd64-xl-multivcpu host-install(3)
broken-step test-amd64-i386-pv host-install(3)
broken-step test-amd64-amd64-xl-qemuu-debianhvm-amd64 host-install(3)
broken-step test-amd64-amd64-xl-qemuu-winxpsp3 host-install(3)
broken-step test-amd64-amd64-libvirt host-install(3)
broken-step test-amd64-amd64-xl-qemuu-win7-amd64 host-install(3)
broken-step test-amd64-i386-libvirt-pair host-install/dst_host(4)
broken-step test-amd64-i386-pair host-install/dst_host(4)
broken-step test-amd64-amd64-pair host-install/src_host(3)
broken-step test-amd64-amd64-libvirt-pair host-install/src_host(3)
Push not applicable.
------------------------------------------------------------
commit e72488cdcf2208f2df334fa88c35b33e695fa93b
Author: P J P <ppandit@redhat.com>
Date: Mon Jul 25 17:37:18 2016 +0530
virtio: error out if guest exceeds virtqueue size
A broken or malicious guest can submit more requests than the virtqueue
size permits.
The guest can submit requests without bothering to wait for completion
and is therefore not bound by virtqueue size. This requires reusing
vring descriptors in more than one request, which is incorrect but
possible. Processing a request allocates a VirtQueueElement and
therefore causes unbounded memory allocation controlled by the guest.
Exit with an error if the guest provides more requests than the
virtqueue size permits. This bounds memory allocation and makes the
buggy guest visible to the user.
upstream-commit-id: afd9096eb1882f23929f5b5c177898ed231bac66
Reported-by: Zhenhao Hong <zhenhaohong@gmail.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
reply other threads:[~2016-07-29 9:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=osstest-66857-mainreport@xen.org \
--to=citrix-osstest@xenproject.org \
--cc=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xensource.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).