|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-unstable-coverity test] 132506: regressions - ALL FAIL
flight 132506 xen-unstable-coverity real [real] http://logs.test-lab.xenproject.org/osstest/logs/132506/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: coverity-amd64 7 coverity-upload fail REGR. vs. 132424 version targeted for testing: xen 3ec62664bdd67dc0c41ff22198c406729b3c87a4 baseline version: xen 08b908ba63dee8bc313983c5e412852cbcbcda85 Last test of basis 132424 2019-01-23 09:19:14 Z 4 days Testing same since 132506 2019-01-27 09:18:42 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Andrii Anisov <andrii_anisov@xxxxxxxx> George Dunlap <george.dunlap@xxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Julien Grall <julien.grall@xxxxxxx> Roger Pau Monné <roger.pau@xxxxxxxxxx> Wei Liu <wei.liu2@xxxxxxxxxx> jobs: coverity-amd64 fail ------------------------------------------------------------ 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 3ec62664bdd67dc0c41ff22198c406729b3c87a4 Author: George Dunlap <george.dunlap@xxxxxxxxxx> Date: Thu Jan 24 17:48:27 2019 +0000 docs: Fix dm_restrict documentation Remove "chatty" and redundant information from the xl man page; restrict it to functional descriptions only, and point instead to qemu-depriv.pandoc and SUPPORT.md as locations for "canonical" information. Add a man page entry for device_model_user. Update qemu-deprivilege.pandoc: Changes in missing feature list: - Migration is functional - But qdisk backends are not Add a missing restriction list. The following statements from the man page are dropped: - Mentioning PV; PV guests never have a device model. - Drop the confusing statement about stdvga and cirrus vga options. - Re-used domain IDs are now handled. - Device models should no longer be able to create world-readable files on dom0's filesystem. Signed-off-by: George Dunlap <george.dunlap@xxxxxxxxxx> Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> Release-acked-by: Juergen Gross <jgross@xxxxxxxx> commit 3389a8dc8c5753a3c84744923cd0193395e3f2a9 Author: Roger Pau Monné <roger.pau@xxxxxxxxxx> Date: Fri Jan 25 09:49:50 2019 +0100 iommu: fix order of arguments in iommu_map call at iommu_hwdom_init The order of the page_order and the flags parameters are inverted in the call to iommu_map made in iommu_hwdom_init. Fixes: e8afe1124cc1 ("iommu: elide flushing for higher order map/unmap operations") Signed-off-by: Roger Pau Monné <roger.pau@xxxxxxxxxx> Reviewed-by: Paul Durrant <paul.durrant@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> Release-acked-by: Juergen Gross <jgross@xxxxxxxx> commit ba9b5a09da01960848ae9d30a34fb9073efb4f13 Author: Roger Pau Monné <roger.pau@xxxxxxxxxx> Date: Fri Jan 25 09:48:38 2019 +0100 amd/iommu: fix present bit checking when clearing PTE The current check for the present bit is wrong, since the present bit is located in the low part of the entry. Fixes: e8afe1124cc1 ("iommu: elide flushing for higher order map/unmap operations") Signed-off-by: Roger Pau Monné <roger.pau@xxxxxxxxxx> Reviewed-by: Paul Durrant <paul.durrant@xxxxxxxxxx> Reviewed-by: Brian Woods <brian.woods@xxxxxxx> Release-acked-by: Juergen Gross <jgross@xxxxxxxx> commit 9e92acf1b752dfdfb294234b32d1fa9f55bfdc0f Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Thu Jul 24 11:06:39 2014 +0100 xen/sched: Introduce domain_vcpu() helper The progression of multi-vcpu support in Xen (originally a single pointer, then an embedded d->vcpu[] array, then a dynamically allocated array) has resulted in a large quantity of ad-hoc code for looking a vcpu up by id, and a large number of ways that the toolstack can cause Xen to trip over a NULL pointer. Some of this has been addressed in Xen 4.12, and work is ongoing. Another property of looking a vcpu up by id is that it is frequently done in unprivileged hypercall context, making it an attractive target for speculative sidechannel attacks. Introduce a helper to do the lookup correctly, and without speculative interference. For performance reasons, it is useful not to have an smp_rmb() in this helper on ARM, and luckily this is safe to do, because of the serialisation offered by the global domlist lock. As a minor change noticed when checking the safety of this construct, sanity check during boot that idle->max_vcpus is a suitable upper bound for idle->vcpu[]. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Release-acked-by: Juergen Gross <jgross@xxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit e3b418ac491919127211b4d3c692d431061d7c09 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Fri Dec 21 17:23:32 2018 +0000 x86/pvh-dom0: Remove unnecessary function pointer call from modify_identity_mmio() Function pointer calls are far more expensive in a post-Spectre world, and this one doesn't need to be. No functional change. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx> Acked-by: Jan Beulich <jbeulich@xxxxxxxx> Release-acked-by: Juergen Gross <jgross@xxxxxxxx> commit e1fe5f9c389286b16171c632b3063bcc65cec07e Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Fri Dec 7 13:43:27 2018 +0000 xen/dom0: Add a dom0-iommu=none option For development purposes, it is very convenient to boot Xen as a PVH guest, with an XTF PV or PVH "dom0". The edit-compile-go cycle is a matter of seconds, and you can reasonably insert printk() debugging in places which which would be completely infeasible when booting fully-fledged guests. However, the PVH dom0 path insists on having a working IOMMU, which doesn't exist when virtualised as a PVH guest, and isn't necessary for XTF anyway. Introduce a developer mode to skip the IOMMU requirement. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Roger Pau Monné <roger.pau@xxxxxxxxxx> Release-acked-by: Juergen Gross <jgross@xxxxxxxx> Acked-by: Jan Beulich <jbeulich@xxxxxxxx> commit b7e8dee07cdc9714d79a2d4eb524c17705a596e4 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Mon Dec 31 14:06:52 2018 +0000 xen/dom0: Deprecate iommu_hwdom_inclusive and leave it disabled by default This option is unique to x86 PV dom0's, but it is not sensible to have a catch-all which blindly maps all non-RAM regions into the IOMMU. The map-reserved option remains, and covers all the buggy firmware issues that I am aware of. The two common cases are legacy USB keyboard emulation, and the BMC mailbox used by vendor firmware in NICs/HBAs to report information back to the iLO/iDRAC/etc for remote remote management purposes. A specific advantage of this change is that x86 dom0's IOMMU setup is now consistent between PV and PVH. This change is not expected to have any impact, due to map-reserved remaining. In the unlikely case that it does cause an issue, we should introduce other map-$SPECIFIC options rather than re-introducing this catch-all. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Release-acked-by: Juergen Gross <jgross@xxxxxxxx> Reviewed-by: Roger Pau Monné <roger.pau@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit 633a4094732100c645c41b0fa9087cb432ca1e11 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Mon Dec 10 21:29:10 2018 +0000 docs: Improve documentation and parsing for efi= Update parse_efi_param() to use parse_boolean() for "rs", so it behaves like other Xen booleans. However, change "attr=uc" to not be a boolean. "no-attr=uc" is ambiguous and shouldn't be accepted, but accept "attr=no" as an acceptable alternative. Update the command line documentation for consistency. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Release-acked-by: Juergen Gross <jgross@xxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit 30f5047b2c4e577436b505ba7627f34c3be02014 Author: Julien Grall <julien.grall@xxxxxxx> Date: Fri Nov 30 17:15:33 2018 +0000 xen/arm: gic: Make sure the number of interrupt lines is valid before using it GICv2 and GICv3 supports up to 1020 interrupts. However, the value computed from GICD_TYPER.ITLinesNumber can be up to 1024. On GICv3, we will end up to write in reserved registers that are right after the IROUTERs one as the value is not capped early enough. Cap the number of interrupts as soon as we compute it so we know we can safely using it afterwards. Signed-off-by: Julien Grall <julien.grall@xxxxxxx> Reported-by: Jan-Peter Larsson <Jan-Peter.Larsson@xxxxxxx> Reviewed-by: Stefano Stabellini <sstabellini@xxxxxxxxxx> Release-Acked-by: Juergen Gross <jgross@xxxxxxxx> commit 9ed527dc95dd8f1871fc5c9f6fa5a58fbd0379a1 Author: Andrii Anisov <andrii_anisov@xxxxxxxx> Date: Wed Jan 23 14:50:07 2019 +0200 arm/p2m: call iommu iotlb flush if iommu exists and enabled Taking decision by `need_iommu_pt_sync()` make us never kicking `iommu_iotlb_flush()` for IOMMUs which do share P2M with CPU. So check `has_iommu_pt()` instead. Signed-off-by: Andrii Anisov <andrii_anisov@xxxxxxxx> Reviewed-by: Paul Durant <paul.durrant@xxxxxxxxxx> Release-Acked-by: Juergen Gross <jgross@xxxxxxxx> Acked-by: Julien Grall <julien.grall@xxxxxxx> (qemu changes not included) _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |