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

[Xen-devel] [xen-unstable-smoke test] 94521: regressions - FAIL

flight 94521 xen-unstable-smoke real [real]

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-amd64-libvirt           5 libvirt-build             fail REGR. vs. 94514

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-libvirt      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                  9e28baf22ec98a64f68757eff39df72173d5f1bb
baseline version:
 xen                  46699c7393bd991234b5642763c5c24b6b39a6c4

Last test of basis    94514  2016-05-17 13:01:58 Z    0 days
Testing same since    94521  2016-05-17 15:03:04 Z    0 days    1 attempts

People who touched revisions under test:
  Jan Beulich <jbeulich@xxxxxxxx>

 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-amd64-libvirt                                          fail    
 test-armhf-armhf-xl                                          pass    
 test-amd64-amd64-xl-qemuu-debianhvm-i386                     pass    
 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

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

Test harness code can be found at

Not pushing.

commit 9e28baf22ec98a64f68757eff39df72173d5f1bb
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Tue May 17 16:42:15 2016 +0200

    x86: make SMEP/SMAP suppression tolerate NMI/MCE at the "wrong" time
    There is one instruction boundary where any kind of interruption would
    break the assumptions cr4_pv32_restore's debug mode checking makes on
    the correlation between the CR4 register value and its in-memory cache.
    Correct this (see the code comment) even in non-debug mode, or else
    a subsequent cr4_pv32_restore would also be misguided into thinking the
    features are enabled when they really aren't.
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Release-acked-by: Wei Liu <wei.liu2@xxxxxxxxxx>

commit e5e73163ec40b409151f2170d8e406a72b515ff2
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Tue May 17 16:41:35 2016 +0200

    x86: refine debugging of SMEP/SMAP fix
    Instead of just latching cr4_pv32_mask into %rdx, correct the found
    wrong value in %cr4 (to avoid triggering another BUG). The value left
    in %rdx should be sufficient for deducing cr4_pv32_mask from the
    register dump.
    Also there is one more place for XEN_CR4_PV32_BITS to be used.
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
    Release-acked-by: Wei Liu <wei.liu2@xxxxxxxxxx>
(qemu changes not included)

Xen-devel mailing list



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