|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-4.1-testing test] 14096: trouble: broken/fail/pass
flight 14096 xen-4.1-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/14096/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-win 3 host-install(3) broken REGR. vs. 13919 test-amd64-i386-rhel6hvm-amd 3 host-install(3) broken REGR. vs. 13919 test-amd64-i386-xl-win-vcpus1 3 host-install(3) broken REGR. vs. 13919 test-amd64-i386-xl-win7-amd64 3 host-install(3) broken REGR. vs. 13919 test-amd64-i386-qemuu-rhel6hvm-amd 3 host-install(3) broken REGR. vs. 13919 test-i386-i386-xl 3 host-install(3) broken REGR. vs. 13919 test-i386-i386-win 3 host-install(3) broken REGR. vs. 13919 test-amd64-amd64-xl-win7-amd64 3 host-install(3) broken REGR. vs. 13919 test-i386-i386-xl-winxpsp3 3 host-install(3) broken REGR. vs. 13919 test-amd64-i386-xend-winxpsp3 3 host-install(3) broken REGR. vs. 13919 test-amd64-i386-xl-multivcpu 3 host-install(3) broken REGR. vs. 13919 test-amd64-amd64-xl-winxpsp3 3 host-install(3) broken REGR. vs. 13919 test-amd64-i386-xl 3 host-install(3) broken REGR. vs. 13919 test-amd64-i386-xl-winxpsp3-vcpus1 3 host-install(3) broken REGR. vs. 13919 test-amd64-amd64-pv 3 host-install(3) broken REGR. vs. 13919 test-i386-i386-xl-qemuu-winxpsp3 3 host-install(3) broken REGR. vs. 13919 test-amd64-i386-xl-credit2 3 host-install(3) broken REGR. vs. 13919 test-amd64-amd64-xl-win 3 host-install(3) broken REGR. vs. 13919 test-i386-i386-pv 3 host-install(3) broken REGR. vs. 13919 test-amd64-i386-win-vcpus1 3 host-install(3) broken REGR. vs. 13919 test-amd64-i386-rhel6hvm-intel 3 host-install(3) broken REGR. vs. 13919 test-amd64-i386-pair 4 host-install/dst_host(4) broken REGR. vs. 13919 test-amd64-i386-pair 3 host-install/src_host(3) broken REGR. vs. 13919 test-amd64-amd64-pair 3 host-install/src_host(3) broken REGR. vs. 13919 test-amd64-amd64-pair 4 host-install/dst_host(4) broken REGR. vs. 13919 test-i386-i386-pair 4 host-install/dst_host(4) broken REGR. vs. 13919 test-i386-i386-pair 3 host-install/src_host(3) broken REGR. vs. 13919 Regressions which are regarded as allowable (not blocking): test-amd64-amd64-xl-sedf 3 host-install(3) broken REGR. vs. 13919 test-amd64-amd64-xl-sedf-pin 3 host-install(3) broken REGR. vs. 13919 test-amd64-amd64-xl-pcipt-intel 3 host-install(3) broken REGR. vs. 13919 Tests which did not succeed, but are not blocking: test-amd64-i386-qemuu-rhel6hvm-intel 11 leak-check/check fail never pass test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop fail never pass test-amd64-amd64-win 16 leak-check/check fail never pass test-i386-i386-xl-win 13 guest-stop fail never pass test-amd64-amd64-xl-qemuu-winxpsp3 13 guest-stop fail never pass version targeted for testing: xen 69d1cc78a5bd baseline version: xen a15596a619ed ------------------------------------------------------------ People who touched revisions under test: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx> Ian Campbell <ian.campbell@xxxxxxxxxx> Ian Jackson <ian.jackson@xxxxxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> ------------------------------------------------------------ jobs: build-amd64 pass build-i386 pass build-amd64-oldkern pass build-i386-oldkern pass build-amd64-pvops pass build-i386-pvops pass test-amd64-amd64-xl pass test-amd64-i386-xl broken test-i386-i386-xl broken test-amd64-i386-rhel6hvm-amd broken test-amd64-i386-qemuu-rhel6hvm-amd broken test-amd64-amd64-xl-qemuu-win7-amd64 fail test-amd64-amd64-xl-win7-amd64 broken test-amd64-i386-xl-win7-amd64 broken test-amd64-i386-xl-credit2 broken test-amd64-amd64-xl-pcipt-intel broken test-amd64-i386-rhel6hvm-intel broken test-amd64-i386-qemuu-rhel6hvm-intel fail test-amd64-i386-xl-multivcpu broken test-amd64-amd64-pair broken test-amd64-i386-pair broken test-i386-i386-pair broken test-amd64-amd64-xl-sedf-pin broken test-amd64-amd64-pv broken test-amd64-i386-pv pass test-i386-i386-pv broken test-amd64-amd64-xl-sedf broken test-amd64-i386-win-vcpus1 broken test-amd64-i386-xl-win-vcpus1 broken test-amd64-i386-xl-winxpsp3-vcpus1 broken test-amd64-amd64-win fail test-amd64-i386-win broken test-i386-i386-win broken test-amd64-amd64-xl-win broken test-i386-i386-xl-win fail test-amd64-amd64-xl-qemuu-winxpsp3 fail test-i386-i386-xl-qemuu-winxpsp3 broken test-amd64-i386-xend-winxpsp3 broken test-amd64-amd64-xl-winxpsp3 broken test-i386-i386-xl-winxpsp3 broken ------------------------------------------------------------ sg-report-flight on woking.cam.xci-test.com logs: /home/xc_osstest/logs images: /home/xc_osstest/images Logs, config files, etc. are available at http://www.chiark.greenend.org.uk/~xensrcts/logs Test harness code can be found at http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary Not pushing. ------------------------------------------------------------ changeset: 23385:69d1cc78a5bd tag: tip user: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> date: Fri Oct 26 16:10:04 2012 +0100 libxc: builder: limit maximum size of kernel/ramdisk. Allowing user supplied kernels of arbitrary sizes, especially during decompression, can swallow up dom0 memory leading to either virtual address space exhaustion in the builder process or allocation failures/OOM killing of both toolstack and unrelated processes. We disable these checks when building in a stub domain for pvgrub since this uses the guest's own memory and is isolated. Decompression of gzip compressed kernels and ramdisks has been safe since 14954:58205257517d (Xen 3.1.0 onwards). This is XSA-25 / CVE-2012-4544. Also make explicit checks for buffer overflows in various decompression routines. These were already ruled out due to other properties of the code but check them as a belt-and-braces measure. Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx> Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> [ Includes 25589:60f09d1ab1fe for CVE-2012-2625 ] changeset: 23384:a15596a619ed user: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx> date: Thu Oct 04 10:44:43 2012 +0200 x86: check remote MMIO remap permissions When a domain is mapping pages from a different pg_owner domain, the iomem_access checks are currently only applied to the pg_owner domain, potentially allowing a domain with a more restrictive iomem_access policy to have the pages mapped into its page tables. To catch this, also check the owner of the page tables. The current domain does not need to be checked because the ability to manipulate a domain's page tables implies full access to the target domain, so checking that domain's permission is sufficient. Signed-off-by: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx> Acked-by: Jan Beulich <jbeulich@xxxxxxxx> xen-unstable changeset: 25952:8278d7d8fa48 xen-unstable date: Wed Sep 26 09:56:07 UTC 2012 ======================================== commit d7d453f51459b591faa96d1c123b5bfff7c5b6b6 Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> Date: Thu Sep 6 17:05:30 2012 +0100 Disable qemu monitor by default. The qemu monitor is an overly powerful feature which must be protected from untrusted (guest) administrators. Neither xl nor xend expect qemu to produce this monitor unless it is explicitly requested. This is a security problem, XSA-19. Previously it was CVE-2007-0998 in Red Hat but we haven't dealt with it in upstream. We hope to have a new CVE for it here but we don't have one yet. Signed-off-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> (cherry picked from commit bacc0d302445c75f18f4c826750fb5853b60e7ca) _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |