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

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

[osstest service owner]

flight 124663 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124663/

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. 124430

version targeted for testing:
 xen                  437211cb696515ee5bd5dae0ab72866c9f382a33
baseline version:
 xen                  988d66cb78c35c620c2a0eb01bac842e4e99bf0e

Last test of basis   124430  2018-06-20 09:18:50 Z    4 days
Testing same since   124663  2018-06-24 09:18:18 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@citrix.com>
  Jan Beulich <jbeulich@suse.com>
  Juergen Gross <jgross@suse.com>

jobs:
 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
    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 437211cb696515ee5bd5dae0ab72866c9f382a33
Author: Jan Beulich <jbeulich@suse.com>
Date:   Thu Jun 21 11:35:46 2018 +0200

    x86/EFI: fix FPU state handling around runtime calls
    
    There are two issues.  First, the nonlazy xstates were never restored
    after returning from the runtime call.
    
    Secondly, with the fully_eager_fpu mitigation for XSA-267 / LazyFPU, the
    unilateral stts() is no longer correct, and hits an assertion later when
    a lazy state restore tries to occur for a fully eager vcpu.
    
    Fix both of these issues by calling vcpu_restore_fpu_eager().  As EFI
    runtime services can be used in the idle context, the idle assertion
    needs to move until after the fully_eager_fpu check.
    
    Introduce a "curr" local variable and replace other uses of "current"
    at the same time.
    
    Reported-by: Andrew Cooper <andrew.cooper3@citrix.com>
    Signed-off-by: Jan Beulich <jbeulich@suse.com>
    Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
    Tested-by: Juergen Gross <jgross@suse.com>
    Release-acked-by: Juergen Gross <jgross@suse.com>
(qemu changes not included)

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel