|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-unstable-smoke test] 87912: regressions - FAIL
flight 87912 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/87912/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 5 xen-build fail REGR. vs. 87376 Tests which did not succeed, but are not blocking: build-amd64-libvirt 1 build-check(1) blocked n/a test-amd64-amd64-libvirt 1 build-check(1) blocked n/a test-amd64-amd64-xl-qemuu-debianhvm-i386 1 build-check(1) blocked n/a test-armhf-armhf-xl 12 migrate-support-check fail never pass test-armhf-armhf-xl 13 saverestore-support-check fail never pass version targeted for testing: xen fab9839e805819b9562c9f00d0105d5e9e03bbdc baseline version: xen 04119085f5a2a135e5161535b8821e1aa0d7db8a Last test of basis 87376 2016-03-25 23:21:00 Z 3 days Failing since 87883 2016-03-29 13:02:02 Z 0 days 3 attempts Testing same since 87912 2016-03-29 17:01:22 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Anthony PERARD <anthony.perard@xxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> Paul Durrant <paul.durrant@xxxxxxxxxx> Shannon Zhao <shannon.zhao@xxxxxxxxxx> Shuai Ruan <shuai.ruan@xxxxxxxxxxxxxxx> Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> Tim Deegan <tim@xxxxxxx> Wei Liu <wei.liu2@xxxxxxxxxx> Zhigang Wang <zhigang.x.wang@xxxxxxxxxx> jobs: build-amd64 fail build-armhf pass build-amd64-libvirt blocked test-armhf-armhf-xl pass test-amd64-amd64-xl-qemuu-debianhvm-i386 blocked test-amd64-amd64-libvirt blocked ------------------------------------------------------------ sg-report-flight on osstest.test-lab.xenproject.org logs: /home/logs/logs images: /home/logs/images Logs, config files, etc. are available at http://logs.test-lab.xenproject.org/osstest/logs Explanation of these reports, and of osstest in general, is at http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master Test harness code can be found at http://xenbits.xen.org/gitweb?p=osstest.git;a=summary Not pushing. ------------------------------------------------------------ commit fab9839e805819b9562c9f00d0105d5e9e03bbdc Author: Zhigang Wang <zhigang.x.wang@xxxxxxxxxx> Date: Wed Mar 23 13:45:37 2016 -0400 tools/python/xc: fix tmem_control parameter parsing There should be 6 instead of 7 arguments now for tmem_control() . which was done in commit 54a51b1766fd433b95e63834eb15d4b1f70271de "tmem: Remove xc_tmem_control mystical arg3" which missed this change. Signed-off-by: Zhigang Wang <zhigang.x.wang@xxxxxxxxxx> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> commit b18c1e6fb93dec9a6861db60af412e4f5a749a04 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Mar 29 17:17:10 2016 +0200 public: drop assembly equates from errno.h again This wasn't a good idea after all - make them unavailable except for legacy code using an older interface version. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: Tim Deegan <tim@xxxxxxx> commit 607044bf9a8c8a8b37666a3a64c0d9b005875b13 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Mar 29 17:16:47 2016 +0200 build: avoid putting local absolute symbols in symbol tables They're not really useful past the building stage and only needlessly increase binary file sizes. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: Tim Deegan <tim@xxxxxxx> commit bb9373a802f5413880dec591a57292a877178d17 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Mar 29 17:16:23 2016 +0200 spinlock: improve spin_is_locked() for recursive locks Recursive locks know their current owner, and since we use the function solely to determine whether a particular lock is being held by the current CPU (which so far has been an imprecise check), make actually check the owner for recusrively acquired locks. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Dario Faggioli <dario.faggioli@xxxxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Quan Xu <quan.xu@xxxxxxxxx> Acked-by: Tim Deegan <tim@xxxxxxx> commit 9979547be5875437abae58401093279113258b18 Author: Shuai Ruan <shuai.ruan@xxxxxxxxxxxxxxx> Date: Tue Mar 29 17:15:57 2016 +0200 x86/xsaves: calculate comp_offsets[] based on xcomp_bv Previous patch using all available features calculate comp_offsets. This is wrong.This patch fix this bug by calculating the comp_offset based on xcomp_bv of current guest. Also, the comp_offset should take alignment into consideration. Reported-by: Jan Beulich <jbeulich@xxxxxxxx> Signed-off-by: Shuai Ruan <shuai.ruan@xxxxxxxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit 3130079f5140afa09093e51dc85b5d1246fab001 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Mar 29 17:15:15 2016 +0200 ns16550: enable Pericom controller support Other than the controllers supported so far, multiple port Pericom boards map all of their ports via BAR0, which requires a number of adjustments: Instead of tracking "max_bars" we now flag whether all ports use BAR0, and whether to expect a port-I/O or MMIO resource. As a result pci_uart_config() now gets handed a port index, which it then maps into a BAR index or an offset into BAR0 depending on the bar0 flag. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Tested-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> Acked-by: Tim Deegan <tim@xxxxxxx> commit cc955d2f08d28873f83c3c30e02421aa91c64966 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Mar 29 17:14:43 2016 +0200 ns16550: store pointer to config parameters for PCI Subsequent changes will want to use this pointer. This makes the enable_ro structure member redundant, so it gets dropped at once. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Tested-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> Acked-by: Tim Deegan <tim@xxxxxxx> commit a43f1e9b9d44eda4dd0338904ab422b4542bd031 Author: Shannon Zhao <shannon.zhao@xxxxxxxxxx> Date: Tue Mar 29 14:26:57 2016 +0200 hvm/params: add a new delivery type for event-channel in HVM_PARAM_CALLBACK_IRQ This new delivery type which is for ARM shares the same value with HVM_PARAM_CALLBACK_TYPE_VECTOR which is for x86. val[15:8] is flag: val[7:0] is a PPI. To the flag, bit 8 stands the interrupt mode is edge(1) or level(0) and bit 9 stands the interrupt polarity is active low(1) or high(0). Signed-off-by: Shannon Zhao <shannon.zhao@xxxxxxxxxx> Acked-by: Jan Beulich <jbeulich@xxxxxxxx> commit b93687291574ee64b8244e15455a71d663787962 Author: Paul Durrant <paul.durrant@xxxxxxxxxx> Date: Tue Mar 29 14:26:33 2016 +0200 x86/hvm/viridian: fix APIC assist page leak Commit a6f2cdb6 "keep APIC assist page mapped..." introduced a page leak because it relied on viridian_vcpu_deinit() always being called to release the page mapping. This does not happen in the case a normal domain shutdown. This patch fixes the problem by introducing a new function, viridian_domain_deinit(), which will iterate through the vCPUs and release any page mappings still present. Signed-off-by: Paul Durrant <paul.durrant@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit 78c5f59ebd79117321a988c200048b5d94aa5df6 Author: Paul Durrant <paul.durrant@xxxxxxxxxx> Date: Tue Mar 29 14:26:03 2016 +0200 x86/hvm/viridian: save APIC assist vector If any vcpu has a pending APIC assist when the domain is suspended then the vector needs to be saved. If this is not done then it's possible for the vector to remain pending in the vlapic ISR indefinitely after resume. This patch adds code to save the APIC assist vector value in the viridian vcpu save record. This means that the record is now zero- extended on load and, because this implies a loaded value of zero means nothing is pending (for backwards compatibility with hosts not implementing APIC assist), the rest of the viridian APIC assist code is adjusted to treat a zero value in this way. A check has therefore been added to viridian_start_apic_assist() to prevent the enlightenment being used for vectors < 0x10 (which are illegal for an APIC). Signed-off-by: Paul Durrant <paul.durrant@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit 966a420c010355bd7c28f8a75e31e713715f6afa Author: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> Date: Tue Mar 29 14:25:43 2016 +0200 Anthony Perard to co-maintain qemu I nominate Anthony Perard as qemu-xen co-maintainer. He has been doing a lot of QEMU work over the years and in fact he is the original author of the Xen enablement code in upstream QEMU. As qemu-xen co-maintainer, he could help me manage the qemu-xen trees and promptly backport all the relevant commits from upstream QEMU. Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> Acked-by: Anthony PERARD <anthony.perard@xxxxxxxxxx> commit 7bd9dc3adfbb014c55f0928ebb3b20950ca9c019 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Mar 29 14:24:26 2016 +0200 x86: fix information leak on AMD CPUs The fix for XSA-52 was wrong, and so was the change synchronizing that new behavior to the FXRSTOR logic: AMD's manuals explictly state that writes to the ES bit are ignored, and it instead gets calculated from the exception and mask bits (it gets set whenever there is an unmasked exception, and cleared otherwise). Hence we need to follow that model in our workaround. This is CVE-2016-3158 / CVE-2016-3159 / XSA-172. [xen/arch/x86/xstate.c:xrstor: CVE-2016-3158] [xen/arch/x86/i387.c:fpu_fxrstor: CVE-2016-3159] Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> (qemu changes not included) _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |