[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[xen-unstable-coverity test] 154954: trouble: broken

flight 154954 xen-unstable-coverity real [real]

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 coverity-amd64                  <job status>                 broken
 coverity-amd64                4 host-install(4)        broken REGR. vs. 154638

version targeted for testing:
 xen                  5bcac985498ed83d89666959175ca9c9ed561ae1
baseline version:
 xen                  2785b2a9e04abc148e1c5259f4faee708ea356f4

Last test of basis   154638  2020-09-23 09:18:27 Z    4 days
Testing same since   154954  2020-09-27 09:18:27 Z    0 days    1 attempts

People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  Jan Beulich <jbeulich@xxxxxxxx>
  Julien Grall <jgrall@xxxxxxxxxx>
  Oleksandr Tyshchenko <oleksandr_tyshchenko@xxxxxxxx>
  Stefano Stabellini <sstabellini@xxxxxxxxxx>

 coverity-amd64                                               broken  

sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images

Logs, config files, etc. are available at

Explanation of these reports, and of osstest in general, is at

Test harness code can be found at

Not pushing.

commit 5bcac985498ed83d89666959175ca9c9ed561ae1
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Mon Jun 29 11:32:37 2020 +0100

    x86/pv: Don't clobber NT on return-to-guest
    A 64bit IRET can restore NT - the faulting case is when NT is set in the 
    flags.  This change had an unintended consequence of causing the NT flag to
    spontaneously disappear from guest context whenever a interrupt/exception
    In combination with a SYSENTER which sets both TF and NT, Xen's handling of
    the #DB exceptions clears NT before it is even recorded suitably in the 
    kernel's view of what userspace was doing.
    Reported-by: Andy Lutomirski <luto@xxxxxxxxxx>
    Fixes: 0e47f92b0 ("x86: force EFLAGS.IF on when exiting to PV guests")
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx>

commit 61d4a04349895edc5a5868274b906ba61ef24f47
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Fri Jun 26 14:56:23 2020 +0100

    x86/pv: Don't deliver #GP for a SYSENTER with NT set
    It is a matter of guest kernel policy what to do with offending userspace, 
    terminating said userspace may not be the action chosen.
    Linux explicitly tolerates this case.
    Reported-by: Andy Lutomirski <luto@xxxxxxxxxx>
    Fixes: fdac951560 ("x86: clear EFLAGS.NT in SYSENTER entry path")
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx>

commit af3c913f03b5f9eab15b168ef87cde80f9addc6e
Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date:   Tue Sep 22 20:05:22 2020 +0100

    x86/msi: Fold pci_conf_write16() calls in write_msi_msg()
    In addition, this removes the unqualified 0/1 passed to msi_data_reg()
    No functional change.
    Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Acked-by: Jan Beulich <jbeulich@xxxxxxxx>

commit 5a37207df52066efefe419c677b089a654d37afc
Author: Julien Grall <jgrall@xxxxxxxxxx>
Date:   Fri Sep 18 18:11:16 2020 +0100

    xen/arm: bootfdt: Ignore empty memory bank
    At the moment, Xen will stop processing the Device Tree if a memory
    bank is empty (size == 0).
    Unfortunately, some of the Device Tree (such as on Colibri imx8qxp)
    may contain such a bank. This means Xen will not be able to boot
    Relax the check to just ignore the banks. FWIW this also seems to be the
    behavior adopted by Linux.
    Reported-by: Daniel Wagner <Daniel.Wagner2@xxxxxxxxxxxxxxxxxx>
    Signed-off-by: Julien Grall <jgrall@xxxxxxxxxx>
    Reviewed-by: Bertrand Marquis <bertrand.marquis@xxxxxxx>
    Acked-by: Stefano Stabellini <sstabellini@xxxxxxxxxx>

commit a6732807d335239fc29bd953538affc458bcc197
Author: Oleksandr Tyshchenko <oleksandr_tyshchenko@xxxxxxxx>
Date:   Sat Sep 19 20:21:22 2020 +0300

    SUPPORT.md: Update status of Renesas IPMMU-VMSA (Arm)
    Mark Renesas IPMMU-VMSA as "Supported, not security supported"
    and remove dependencies on CONFIG_EXPERT.
    We can't treat the IOMMU driver as "Supported" since the device
    passthrough feature is not security supported on Arm today.
    Signed-off-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@xxxxxxxx>
    Acked-by: Julien Grall <jgrall@xxxxxxxxxx>
    Acked-by: Stefano Stabellini <sstabellini@xxxxxxxxxx>
(qemu changes not included)



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.