flight 167428 xen-unstable-coverity real [real] flight 167430 xen-unstable-coverity real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/167428/ http://logs.test-lab.xenproject.org/osstest/logs/167430/
Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: coverity-amd64 7 coverity-upload fail REGR. vs. 167384 version targeted for testing: xen 249e0f1d8f203188ccdcced5a05c2149739e1566 baseline version: xen df3e1a5efe700a9f59eced801cac73f9fd02a0e2 Last test of basis 167384 2021-12-12 09:20:52 Z 3 days Testing same since 167428 2021-12-15 09:21:06 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <[email protected]> Anthony PERARD <[email protected]> Jan Beulich <[email protected]> Juergen Gross <[email protected]> Julien Grall <[email protected]> Oleksandr Andrushchenko <[email protected]> Paul Durrant <[email protected]> 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 249e0f1d8f203188ccdcced5a05c2149739e1566 Author: Andrew Cooper <[email protected]> Date: Mon Dec 13 20:33:42 2021 +0000 x86/cpuid: Fix TSXLDTRK definition TSXLDTRK lives in CPUID leaf 7[0].edx, not 7[0].ecx. Bit 16 in ecx is LA57. Fixes: a6d1b558471f ("x86emul: support X{SUS,RES}LDTRK") Signed-off-by: Andrew Cooper <[email protected]> Reviewed-by: Jan Beulich <[email protected]> commit 1382241fe880d48e109f2056cec052bb3919a9d1 Author: Juergen Gross <[email protected]> Date: Tue Dec 14 09:50:07 2021 +0100 perfc: drop calls_to_multicall performance counter The calls_to_multicall performance counter is basically redundant to the multicall hypercall counter. The only difference is the counting of continuation calls, which isn't really that interesting. Drop the calls_to_multicall performance counter. Suggested-by: Jan Beulich <[email protected]> Signed-off-by: Juergen Gross <[email protected]> Reviewed-by: Jan Beulich <[email protected]> commit 668dd44902bbaf52f8e7214e0da060b6ec962e88 Author: Juergen Gross <[email protected]> Date: Tue Dec 14 09:49:23 2021 +0100 x86/perfc: add hypercall performance counters for hvm, correct pv The HVM hypercall handler is missing incrementing the per hypercall counters. Add that. The counters for PV are handled wrong, as they are not using perf_incra() with the number of the hypercall as index, but are incrementing the first hypercall entry (set_trap_table) for each hypercall. Fix that. Signed-off-by: Juergen Gross <[email protected]> Reviewed-by: Jan Beulich <[email protected]> commit 7b99e7258559c9caa235d9faf323b22c68e4a581 Author: Jan Beulich <[email protected]> Date: Tue Dec 14 09:48:17 2021 +0100 x86emul: drop "seg" parameter from insn_fetch() hook This is specified (and asserted for in a number of places) to always be CS. Passing this as an argument in various places is therefore pointless. The price to pay is two simple new functions, with the benefit of the PTWR case now gaining a more appropriate error code. Signed-off-by: Jan Beulich <[email protected]> Reviewed-by: Andrew Cooper <[email protected]> Acked-by: Paul Durrant <[email protected]> commit c49ee0329ff3de98722fd74ed5ba6d9665701e54 Author: Jan Beulich <[email protected]> Date: Tue Dec 14 09:47:31 2021 +0100 SUPPORT.md: limit security support for hosts with very much memory Sufficient and in particular regular testing on very large hosts cannot currently be guaranteed. Anyone wanting us to support larger hosts is free to propose so, but will need to supply not only test results, but also a test plan. This is a follow-up to XSA-385. Signed-off-by: Jan Beulich <[email protected]> Acked-by: Andrew Cooper <[email protected]> Acked-by: Julien Grall <[email protected]> commit 53ed194539ddbea4f6aecb1b7c2f33aa8c0201d9 Author: Jan Beulich <[email protected]> Date: Tue Dec 14 09:46:48 2021 +0100 x86/monitor: don't open-code hvm_has_set_descriptor_access_exiting() Signed-off-by: Jan Beulich <[email protected]> Acked-by: Andrew Cooper <[email protected]> Reviewed by: Alexandru Isaila <[email protected]> commit 7dc0233f534f64e7f3ee71e74e05dd5ab8a24808 Author: Oleksandr Andrushchenko <[email protected]> Date: Tue Dec 14 09:44:44 2021 +0100 vpci: fix function attributes for vpci_process_pending vpci_process_pending is defined with different attributes, e.g. with __must_check if CONFIG_HAS_VPCI enabled and not otherwise. Fix this by defining both of the definitions with __must_check. Fixes: 14583a590783 ("7fbb096bf345 kconfig: don't select VPCI if building a shim-only binary") Signed-off-by: Oleksandr Andrushchenko <[email protected]> Reviewed-by: Julien Grall <[email protected]> Reviewed-by: Roger Pau Monné <[email protected]> commit d828caa9aeee80c59a35f662f875f6573e9b532f Author: Andrew Cooper <[email protected]> Date: Mon Dec 13 17:50:48 2021 +0000 tools/libfsimage: Fix SONAME This gets missed on each release. Follow the same example as libs.mk and pick the version up dynamically. Fixes: a5706b80f42e ("Set version to 4.17: rerun autogen.sh") Suggested-by: Anthony PERARD <[email protected]> Signed-off-by: Andrew Cooper <[email protected]> Acked-by: Anthony PERARD <[email protected]> (qemu changes not included)
