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

[Xen-devel] [xen-unstable test] 9748: regressions - FAIL



flight 9748 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/9748/

Regressions :-(

Tests which did not succeed and are blocking:
 test-amd64-i386-win          15 guest-destroy              fail REGR. vs. 9747

Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
 test-amd64-amd64-xl-pcipt-intel  9 guest-start                 fail never pass
 test-amd64-i386-rhel6hvm-intel  9 guest-start.2                fail never pass
 test-amd64-i386-rhel6hvm-amd  9 guest-start.2                fail   never pass
 test-amd64-i386-win-vcpus1   16 leak-check/check             fail   never pass
 test-amd64-i386-xl-win-vcpus1 13 guest-stop                   fail  never pass
 test-amd64-amd64-win         16 leak-check/check             fail   never pass
 test-amd64-amd64-xl-win      13 guest-stop                   fail   never pass
 test-i386-i386-win           16 leak-check/check             fail   never pass
 test-i386-i386-xl-win        13 guest-stop                   fail   never pass

version targeted for testing:
 xen                  44d925615ac6
baseline version:
 xen                  4699decb8424

------------------------------------------------------------
People who touched revisions under test:
  Ian Campbell <ian.campbell@xxxxxxxxxx>
  Jan Beulich <jbeulich@xxxxxxxx>
  Keir Fraser <keir@xxxxxxx>
  Lasse Collin <lasse.collin@xxxxxxxxxxx>
  Phillip Lougher <phillip@xxxxxxxxxxxxxxxxxxx>
  Wei Wang <wei.wang2@xxxxxxx>
------------------------------------------------------------

jobs:
 build-amd64                                                  pass    
 build-i386                                                   pass    
 build-amd64-oldkern                                          pass    
 build-i386-oldkern                                           pass    
 build-amd64-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-xl                                          pass    
 test-amd64-i386-xl                                           pass    
 test-i386-i386-xl                                            pass    
 test-amd64-i386-rhel6hvm-amd                                 fail    
 test-amd64-i386-xl-credit2                                   pass    
 test-amd64-amd64-xl-pcipt-intel                              fail    
 test-amd64-i386-rhel6hvm-intel                               fail    
 test-amd64-i386-xl-multivcpu                                 pass    
 test-amd64-amd64-pair                                        pass    
 test-amd64-i386-pair                                         pass    
 test-i386-i386-pair                                          pass    
 test-amd64-amd64-pv                                          pass    
 test-amd64-i386-pv                                           pass    
 test-i386-i386-pv                                            pass    
 test-amd64-amd64-xl-sedf                                     pass    
 test-amd64-i386-win-vcpus1                                   fail    
 test-amd64-i386-xl-win-vcpus1                                fail    
 test-amd64-amd64-win                                         fail    
 test-amd64-i386-win                                          fail    
 test-i386-i386-win                                           fail    
 test-amd64-amd64-xl-win                                      fail    
 test-i386-i386-xl-win                                        fail    


------------------------------------------------------------
sg-report-flight on woking.cam.xci-test.com
logs: /home/xc_osstest/logs
images: /home/xc_osstest/images

Logs, config files, etc. are available at
    http://www.chiark.greenend.org.uk/~xensrcts/logs

Test harness code can be found at
    http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary


Not pushing.

------------------------------------------------------------
changeset:   24134:44d925615ac6
tag:         tip
user:        Lasse Collin <lasse.collin@xxxxxxxxxxx>
date:        Fri Nov 11 14:35:51 2011 +0100
    
    Decompressors: check input size in unlzo.c
    
    From: Lasse Collin <lasse.collin@xxxxxxxxxxx>
    
    The code assumes that the input is valid and not truncated.  Add checks to
    avoid reading past the end of the input buffer.  Change the type of "skip"
    from u8 to int to fix a possible integer overflow.
    
    Signed-off-by: Lasse Collin <lasse.collin@xxxxxxxxxxx>
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Keir Fraser <keir@xxxxxxx>
    Committed-by: Jan Beulich <jbeulich@xxxxxxxx>
    
    
changeset:   24133:276db7ceeb5d
user:        Lasse Collin <lasse.collin@xxxxxxxxxxx>
date:        Fri Nov 11 14:35:05 2011 +0100
    
    Decompressors: check for write errors in unlzo.c
    
    From: Lasse Collin <lasse.collin@xxxxxxxxxxx>
    
    The return value of flush() is not checked in unlzo().  This means that
    the decompressor won't stop even if the caller doesn't want more data.
    This can happen e.g.  with a corrupt LZO-compressed initramfs image.
    
    Signed-off-by: Lasse Collin <lasse.collin@xxxxxxxxxxx>
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Keir Fraser <keir@xxxxxxx>
    Committed-by: Jan Beulich <jbeulich@xxxxxxxx>
    
    
changeset:   24132:88347644935e
user:        Lasse Collin <lasse.collin@xxxxxxxxxxx>
date:        Fri Nov 11 14:34:24 2011 +0100
    
    Decompressors: validate match distance in unlzma.c
    
    From: Lasse Collin <lasse.collin@xxxxxxxxxxx>
    
    Validate the newly decoded distance (rep0) in process_bit1().  This is to
    detect corrupt LZMA data quickly.  The old code can run for long time
    producing garbage until it hits the end of the input.
    
    Signed-off-by: Lasse Collin <lasse.collin@xxxxxxxxxxx>
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Keir Fraser <keir@xxxxxxx>
    Committed-by: Jan Beulich <jbeulich@xxxxxxxx>
    
    
changeset:   24131:2ffeeb28e9be
user:        Lasse Collin <lasse.collin@xxxxxxxxxxx>
date:        Fri Nov 11 14:33:30 2011 +0100
    
    Decompressors: check for write errors in unlzma.c
    
    From: Lasse Collin <lasse.collin@xxxxxxxxxxx>
    
    The return value of wr->flush() is not checked in write_byte().  This
    means that the decompressor won't stop even if the caller doesn't want
    more data.  This can happen e.g.  with corrupt LZMA-compressed initramfs.
    Returning the error quickly allows the user to see the error message
    quicker.
    
    There is a similar missing check for wr.flush() near the end of unlzma().
    
    Signed-off-by: Lasse Collin <lasse.collin@xxxxxxxxxxx>
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Keir Fraser <keir@xxxxxxx>
    Committed-by: Jan Beulich <jbeulich@xxxxxxxx>
    
    
changeset:   24130:fe9a59ff8475
user:        Lasse Collin <lasse.collin@xxxxxxxxxxx>
date:        Fri Nov 11 14:32:57 2011 +0100
    
    Decompressors: check for read errors in unlzma.c
    
    From: Lasse Collin <lasse.collin@xxxxxxxxxxx>
    
    Return value of rc->fill() is checked in rc_read() and error() is called
    when needed, but then the code continues as if nothing had happened.
    
    rc_read() is a void function and it's on the top of performance critical
    call stacks, so propagating the error code via return values doesn't sound
    like the best fix.  It seems better to check rc->buffer_size (which holds
    the return value of rc->fill()) in the main loop.  It does nothing bad
    that the code runs a little with unknown data after a failed rc->fill().
    
    This fixes an infinite loop in initramfs decompression if the
    LZMA-compressed initramfs image is corrupt.
    
    Signed-off-by: Lasse Collin <lasse.collin@xxxxxxxxxxx>
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Keir Fraser <keir@xxxxxxx>
    Committed-by: Jan Beulich <jbeulich@xxxxxxxx>
    
    
changeset:   24129:71abe73298b3
user:        Lasse Collin <lasse.collin@xxxxxxxxxxx>
date:        Fri Nov 11 14:32:03 2011 +0100
    
    Decompressors: fix header validation in unlzma.c
    
    From: Lasse Collin <lasse.collin@xxxxxxxxxxx>
    
    Validation of header.pos calls error() but doesn't make the function
    return to indicate an error to the caller.  Instead the decoding is
    attempted with invalid header.pos.  This fixes it.
    
    Signed-off-by: Lasse Collin <lasse.collin@xxxxxxxxxxx>
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Keir Fraser <keir@xxxxxxx>
    Committed-by: Jan Beulich <jbeulich@xxxxxxxx>
    
    
changeset:   24128:7c5eb2265fba
user:        Lasse Collin <lasse.collin@xxxxxxxxxxx>
date:        Fri Nov 11 14:31:38 2011 +0100
    
    Decompressors: remove unused function from unlzma.c
    
    From: Lasse Collin <lasse.collin@xxxxxxxxxxx>
    
    Signed-off-by: Lasse Collin <lasse.collin@xxxxxxxxxxx>
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Keir Fraser <keir@xxxxxxx>
    Committed-by: Jan Beulich <jbeulich@xxxxxxxx>
    
    
changeset:   24127:57db49cf1188
user:        Phillip Lougher <phillip@xxxxxxxxxxxxxxxxxxx>
date:        Fri Nov 11 14:30:36 2011 +0100
    
    bzip2: Add missing checks for malloc returning NULL
    
    From: Phillip Lougher <phillip@xxxxxxxxxxxxxxxxxxx>
    
    Signed-off-by: Phillip Lougher <phillip@xxxxxxxxxxxxxxxxxxx>
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Keir Fraser <keir@xxxxxxx>
    Committed-by: Jan Beulich <jbeulich@xxxxxxxx>
    
    
changeset:   24126:b2891cecc676
user:        Lasse Collin <lasse.collin@xxxxxxxxxxx>
date:        Fri Nov 11 14:29:21 2011 +0100
    
    Decompressors: get rid of set_error_fn() macro
    
    From: Lasse Collin <lasse.collin@xxxxxxxxxxx>
    
    set_error_fn() is a useless complication. Only unlzma.c had some use
    for it and that was easy to change too.
    
    This also gets rid of the static function pointer "error".
    
    Signed-off-by: Lasse Collin <lasse.collin@xxxxxxxxxxx>
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Keir Fraser <keir@xxxxxxx>
    Committed-by: Jan Beulich <jbeulich@xxxxxxxx>
    
    
changeset:   24125:b44278816b72
user:        Jan Beulich <jbeulich@xxxxxxxx>
date:        Fri Nov 11 14:27:41 2011 +0100
    
    multicall: don't ignore failure from __copy_to_guest() upon preemption
    
    At once adjust perf counter updates to also count calls from here even
    if a guest memory access failed.
    
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Keir Fraser <keir@xxxxxxx>
    
    
changeset:   24124:69f8b6f4c29c
user:        Jan Beulich <jbeulich@xxxxxxxx>
date:        Fri Nov 11 14:26:48 2011 +0100
    
    x86/amd-ucode: further turn down verbosity
    
    Turn up the log level on various (mostly debug-only) messages.
    
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Keir Fraser <keir@xxxxxxx>
    
    
changeset:   24123:8b08b2166aa8
user:        Jan Beulich <jbeulich@xxxxxxxx>
date:        Fri Nov 11 14:25:16 2011 +0100
    
    x86: quiesce cpuidle code
    
    So far these messages got pointlessly (as the code in other places
    assumes symmetric configuration) emitted once per CPU. Hide the debug
    one behind opt_cpu_info, and issue the info one just once (if the code
    gets adjusted to support assymtric configurations, this would need to
    be revisited, but ideally without producing per-CPU messages again).
    
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Keir Fraser <keir@xxxxxxx>
    
    
changeset:   24122:4699decb8424
user:        Wei Wang <wei.wang2@xxxxxxx>
date:        Fri Nov 11 12:06:01 2011 +0100
    
    amd iommu: Introduce iommu_has_cap() function
    
    Signed-off-by: Wei Wang <wei.wang2@xxxxxxx>
    Committed-by: Jan Beulich <jbeulich@xxxxxxxx>
    
    
========================================
commit 52834188eedfbbca5636fd869d4c86b3b3044439
Author: Ian Campbell <ian.campbell@xxxxxxxxxx>
Date:   Tue Nov 1 18:42:55 2011 +0000

    qemu-xen: remove i386-dm/README.hvm-pv-magic-ioport-disable
    
    I have just proposed a patch to add this to xen-unstable.hg as
    docs/misc/hvm-emulated-unplug.markdown. This repo is not a place where 
people
    look for docs, plus we are transitioning to upstream qemu.
    
    Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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