[Xen-devel] [qemu-upstream-4.4-testing test] 60156: regressions - FAIL

[osstest service owner <osstest-admin@xxxxxxxxxxxxxx>]

flight 60156 qemu-upstream-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/60156/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-i386-xl-qemuu-win7-amd64 15 guest-localmigrate/x10 fail REGR. vs. 
58380

Regressions which are regarded as allowable (not blocking):
 test-amd64-i386-libvirt      11 guest-start                  fail   like 58380
 test-amd64-amd64-libvirt     11 guest-start                  fail   like 58380

Tests which did not succeed, but are not blocking:
 test-amd64-i386-libvirt-qcow2  9 debian-di-install            fail  never pass
 test-amd64-amd64-xl-raw       9 debian-di-install            fail   never pass
 test-amd64-i386-libvirt-raw  11 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt-qcow2 11 migrate-support-check        fail never pass
 test-amd64-amd64-libvirt-raw 11 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt-vhd 11 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt-vhd  11 migrate-support-check        fail   never pass
 test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop             fail never pass

version targeted for testing:
 qemuu                5d25ace303e36814dc7241e6182bcc8933e5c6dc
baseline version:
 qemuu                32226f429cca6c79826364d8d18acb2226f2f102

Last test of basis    58380  2015-06-10 17:15:50 Z   51 days
Failing since         59500  2015-07-13 10:48:26 Z   18 days    2 attempts
Testing same since    60156  2015-07-30 18:41:56 Z    1 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Kevin Wolf <kwolf@xxxxxxxxxx>
  Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>

jobs:
 build-amd64-xend                                             pass    
 build-i386-xend                                              pass    
 build-amd64                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          pass    
 build-i386-libvirt                                           pass    
 build-amd64-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-xl                                          pass    
 test-amd64-i386-xl                                           pass    
 test-amd64-i386-qemuu-rhel6hvm-amd                           pass    
 test-amd64-amd64-xl-qemuu-debianhvm-amd64                    pass    
 test-amd64-i386-xl-qemuu-debianhvm-amd64                     pass    
 test-amd64-i386-freebsd10-amd64                              pass    
 test-amd64-amd64-xl-qemuu-ovmf-amd64                         pass    
 test-amd64-i386-xl-qemuu-ovmf-amd64                          pass    
 test-amd64-amd64-xl-qemuu-win7-amd64                         fail    
 test-amd64-i386-xl-qemuu-win7-amd64                          fail    
 test-amd64-amd64-xl-credit2                                  pass    
 test-amd64-i386-freebsd10-i386                               pass    
 test-amd64-i386-qemuu-rhel6hvm-intel                         pass    
 test-amd64-amd64-libvirt                                     fail    
 test-amd64-i386-libvirt                                      fail    
 test-amd64-amd64-xl-multivcpu                                pass    
 test-amd64-amd64-pair                                        pass    
 test-amd64-i386-pair                                         pass    
 test-amd64-amd64-pv                                          pass    
 test-amd64-i386-pv                                           pass    
 test-amd64-amd64-amd64-pvgrub                                pass    
 test-amd64-amd64-i386-pvgrub                                 pass    
 test-amd64-amd64-pygrub                                      pass    
 test-amd64-amd64-libvirt-qcow2                               pass    
 test-amd64-i386-libvirt-qcow2                                fail    
 test-amd64-amd64-xl-qcow2                                    pass    
 test-amd64-i386-xl-qcow2                                     pass    
 test-amd64-amd64-libvirt-raw                                 pass    
 test-amd64-i386-libvirt-raw                                  pass    
 test-amd64-amd64-xl-raw                                      fail    
 test-amd64-i386-xl-raw                                       pass    
 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1                     pass    
 test-amd64-amd64-libvirt-vhd                                 pass    
 test-amd64-i386-libvirt-vhd                                  pass    
 test-amd64-amd64-xl-vhd                                      pass    
 test-amd64-i386-xl-vhd                                       pass    
 test-amd64-amd64-xl-qemuu-winxpsp3                           pass    


------------------------------------------------------------
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 5d25ace303e36814dc7241e6182bcc8933e5c6dc
Author: Kevin Wolf <kwolf@xxxxxxxxxx>
Date:   Sun Jul 26 23:42:53 2015 -0400

    ide: Clear DRQ after handling all expected accesses (CVE-2015-5154)
    
    This is additional hardening against an end_transfer_func that fails to
    clear the DRQ status bit. The bit must be unset as soon as the PIO
    transfer has completed, so it's better to do this in a central place
    instead of duplicating the code in all commands (and forgetting it in
    some).
    
    upstream-commit-id: cb72cba83021fa42719e73a5249c12096a4d1cfc
    
    Signed-off-by: Kevin Wolf <kwolf@xxxxxxxxxx>
    Reviewed-by: John Snow <jsnow@xxxxxxxxxx>
    Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>

commit 99559e901d462e7955c077d182bf02d3cdad8e08
Author: Kevin Wolf <kwolf@xxxxxxxxxx>
Date:   Sun Jul 26 23:42:53 2015 -0400

    ide/atapi: Fix START STOP UNIT command completion (CVE-2015-5154)
    
    The command must be completed on all code paths. START STOP UNIT with
    pwrcnd set should succeed without doing anything.
    
    upstream-commit-id: 03441c3a4a42beb25460dd11592539030337d0f8
    
    Signed-off-by: Kevin Wolf <kwolf@xxxxxxxxxx>
    Reviewed-by: John Snow <jsnow@xxxxxxxxxx>
    Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>

commit 17bcea235dcb9da9b917da8453e56e259acd2d34
Author: Kevin Wolf <kwolf@xxxxxxxxxx>
Date:   Sun Jul 26 23:42:53 2015 -0400

    ide: Check array bounds before writing to io_buffer (CVE-2015-5154)
    
    If the end_transfer_func of a command is called because enough data has
    been read or written for the current PIO transfer, and it fails to
    correctly call the command completion functions, the DRQ bit in the
    status register and s->end_transfer_func may remain set. This allows the
    guest to access further bytes in s->io_buffer beyond s->data_end, and
    eventually overflowing the io_buffer.
    
    One case where this currently happens is emulation of the ATAPI command
    START STOP UNIT.
    
    This patch fixes the problem by adding explicit array bounds checks
    before accessing the buffer instead of relying on end_transfer_func to
    function correctly.
    
    upstream-commit-id: d2ff85854512574e7209f295e87b0835d5b032c6
    
    Cc: qemu-stable@xxxxxxxxxx
    Signed-off-by: Kevin Wolf <kwolf@xxxxxxxxxx>
    Reviewed-by: John Snow <jsnow@xxxxxxxxxx>
    Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel