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

[Xen-devel] [linux-linus test] 32616: regressions - FAIL

flight 32616 linux-linus real [real]

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-amd64-xl-qemuu-win7-amd64  7 windows-install   fail REGR. vs. 32564

Regressions which are regarded as allowable (not blocking):
 test-amd64-i386-freebsd10-i386  7 freebsd-install              fail like 32564
 test-amd64-i386-freebsd10-amd64  7 freebsd-install             fail like 32564
 test-amd64-i386-pair        17 guest-migrate/src_host/dst_host fail like 32564
 test-amd64-amd64-xl-qemuu-winxpsp3  7 windows-install          fail like 32564

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-xl-pvh-intel  9 guest-start                  fail  never pass
 test-amd64-i386-libvirt       9 guest-start                  fail   never pass
 test-amd64-amd64-xl-pvh-amd   9 guest-start                  fail   never pass
 test-amd64-amd64-libvirt      9 guest-start                  fail   never pass
 test-armhf-armhf-libvirt      9 guest-start                  fail   never pass
 test-amd64-amd64-xl-pcipt-intel  9 guest-start                 fail never pass
 test-armhf-armhf-xl          10 migrate-support-check        fail   never pass
 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 14 guest-stop         fail never pass
 test-amd64-i386-xl-qemuu-winxpsp3 14 guest-stop                fail never pass
 test-amd64-i386-xl-qemut-win7-amd64 14 guest-stop              fail never pass
 test-amd64-i386-xl-win7-amd64 14 guest-stop                   fail  never pass
 test-amd64-i386-xl-qemuu-win7-amd64 14 guest-stop              fail never pass
 test-amd64-amd64-xl-win7-amd64 14 guest-stop                   fail never pass
 test-amd64-amd64-xl-qemut-winxpsp3 14 guest-stop               fail never pass
 test-amd64-i386-xl-winxpsp3-vcpus1 14 guest-stop               fail never pass
 test-amd64-i386-xl-qemut-winxpsp3-vcpus1 14 guest-stop         fail never pass
 test-amd64-i386-xl-winxpsp3  14 guest-stop                   fail   never pass
 test-amd64-amd64-xl-qemut-win7-amd64 14 guest-stop             fail never pass
 test-amd64-i386-xl-qemut-winxpsp3 14 guest-stop                fail never pass
 test-amd64-amd64-xl-winxpsp3 14 guest-stop                   fail   never pass

version targeted for testing:
 linux                53262d12d1658669029ab39a63e3d314108abe66
baseline version:
 linux                97bf6af1f928216fd6c5a66e8a57bfa95a659672

People who touched revisions under test:
  Alex Chen <alex.chen@xxxxxxxxxx>
  Catalin Marinas <catalin.marinas@xxxxxxx>
  Davidlohr Bueso <dave@xxxxxxxxxxxx>
  Joe Thornber <ejt@xxxxxxxxxx>
  Jungseok Lee <jungseoklee85@xxxxxxxxx>
  Kirill A. Shutemov <kirill.shutemov@xxxxxxxxxxxxxxx>
  Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
  Lorenzo Pieralisi <lorenzo.pieralisi@xxxxxxx>
  Marc Dionne <marc.c.dionne@xxxxxxxxx>
  Marc Dionne <marc.dionne@xxxxxxxxxxxxxxxxxxxx>
  Mike Snitzer <snitzer@xxxxxxxxxx>
  Will Deacon <will.deacon@xxxxxxx>
  zhendong chen <alex.chen@xxxxxxxxxx>

 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          pass    
 build-armhf-libvirt                                          pass    
 build-i386-libvirt                                           pass    
 build-amd64-pvops                                            pass    
 build-armhf-pvops                                            pass    
 build-i386-pvops                                             pass    
 build-amd64-rumpuserxen                                      pass    
 build-i386-rumpuserxen                                       pass    
 test-amd64-amd64-xl                                          pass    
 test-armhf-armhf-xl                                          pass    
 test-amd64-i386-xl                                           pass    
 test-amd64-amd64-xl-pvh-amd                                  fail    
 test-amd64-i386-rhel6hvm-amd                                 pass    
 test-amd64-i386-qemut-rhel6hvm-amd                           pass    
 test-amd64-i386-qemuu-rhel6hvm-amd                           pass    
 test-amd64-amd64-xl-qemut-debianhvm-amd64                    pass    
 test-amd64-i386-xl-qemut-debianhvm-amd64                     pass    
 test-amd64-amd64-xl-qemuu-debianhvm-amd64                    pass    
 test-amd64-i386-xl-qemuu-debianhvm-amd64                     pass    
 test-amd64-i386-freebsd10-amd64                              fail    
 test-amd64-amd64-xl-qemuu-ovmf-amd64                         pass    
 test-amd64-i386-xl-qemuu-ovmf-amd64                          pass    
 test-amd64-amd64-rumpuserxen-amd64                           pass    
 test-amd64-amd64-xl-qemut-win7-amd64                         fail    
 test-amd64-i386-xl-qemut-win7-amd64                          fail    
 test-amd64-amd64-xl-qemuu-win7-amd64                         fail    
 test-amd64-i386-xl-qemuu-win7-amd64                          fail    
 test-amd64-amd64-xl-win7-amd64                               fail    
 test-amd64-i386-xl-win7-amd64                                fail    
 test-amd64-i386-xl-credit2                                   pass    
 test-amd64-i386-freebsd10-i386                               fail    
 test-amd64-i386-rumpuserxen-i386                             pass    
 test-amd64-amd64-xl-pcipt-intel                              fail    
 test-amd64-amd64-xl-pvh-intel                                fail    
 test-amd64-i386-rhel6hvm-intel                               pass    
 test-amd64-i386-qemut-rhel6hvm-intel                         pass    
 test-amd64-i386-qemuu-rhel6hvm-intel                         pass    
 test-amd64-amd64-libvirt                                     fail    
 test-armhf-armhf-libvirt                                     fail    
 test-amd64-i386-libvirt                                      fail    
 test-amd64-i386-xl-multivcpu                                 pass    
 test-amd64-amd64-pair                                        pass    
 test-amd64-i386-pair                                         fail    
 test-amd64-amd64-xl-sedf-pin                                 pass    
 test-amd64-amd64-xl-sedf                                     pass    
 test-amd64-i386-xl-qemut-winxpsp3-vcpus1                     fail    
 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1                     fail    
 test-amd64-i386-xl-winxpsp3-vcpus1                           fail    
 test-amd64-amd64-xl-qemut-winxpsp3                           fail    
 test-amd64-i386-xl-qemut-winxpsp3                            fail    
 test-amd64-amd64-xl-qemuu-winxpsp3                           fail    
 test-amd64-i386-xl-qemuu-winxpsp3                            fail    
 test-amd64-amd64-xl-winxpsp3                                 fail    
 test-amd64-i386-xl-winxpsp3                                  fail    

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

Logs, config files, etc. are available at

Test harness code can be found at

Not pushing.

commit 53262d12d1658669029ab39a63e3d314108abe66
Merge: aa39477 5d96e0c
Author: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Date:   Tue Dec 23 11:03:28 2014 -0800

    Merge tag 'arm64-fixes' of 
    Pull arm64 fixes from Catalin Marinas:
     - __cpu_suspend mm switching fix after warm boot
     - arch_setup_dma_ops implementation
     - pgd_page compilation error fix
     - defconfig updates
    * tag 'arm64-fixes' of 
      arm64: mm: Add pgd_page to support RCU fast_gup
      arm64: defconfig: defconfig update for 3.19
      arm64: kernel: fix __cpu_suspend mm switch on warm-boot
      arm64: Replace set_arch_dma_coherent_ops with arch_setup_dma_ops

commit 5d96e0cba26323c3daeb9f7cdfd4efe70985e2c6
Author: Jungseok Lee <jungseoklee85@xxxxxxxxx>
Date:   Sat Dec 20 00:49:40 2014 +0000

    arm64: mm: Add pgd_page to support RCU fast_gup
    This patch adds pgd_page definition in order to keep supporting
    HAVE_GENERIC_RCU_GUP configuration. In addition, it changes pud_page
    expression to align with pmd_page for readability.
    An introduction of pgd_page resolves the following build breakage
    under 4KB + 4Level memory management combo.
    mm/gup.c: In function 'gup_huge_pgd':
    mm/gup.c:889:2: error: implicit declaration of function 'pgd_page' 
      head = pgd_page(orig);
    mm/gup.c:889:7: warning: assignment makes pointer from integer without a 
      head = pgd_page(orig);
    Cc: Will Deacon <will.deacon@xxxxxxx>
    Cc: Steve Capper <steve.capper@xxxxxxxxxx>
    Signed-off-by: Jungseok Lee <jungseoklee85@xxxxxxxxx>
    [catalin.marinas@xxxxxxx: remove duplicate pmd_page definition]
    Signed-off-by: Catalin Marinas <catalin.marinas@xxxxxxx>

commit f7bf130ecd01f6c9d95c02c7a83d5d9dc263b0c9
Author: Will Deacon <will.deacon@xxxxxxx>
Date:   Sun Dec 21 11:13:12 2014 +0000

    arm64: defconfig: defconfig update for 3.19
    The usual defconfig tweaks, this time:
      - FHANDLE and AUTOFS4_FS to keep systemd happy
      - PID_NS, QUOTA and KEYS to keep LTP happy
      - Disable DEBUG_PREEMPT, as this *really* hurts performance
    Signed-off-by: Will Deacon <will.deacon@xxxxxxx>
    Signed-off-by: Catalin Marinas <catalin.marinas@xxxxxxx>

commit f43c27188a49111b58e9611afa2f0365b0b55625
Author: Lorenzo Pieralisi <lorenzo.pieralisi@xxxxxxx>
Date:   Fri Dec 19 17:03:47 2014 +0000

    arm64: kernel: fix __cpu_suspend mm switch on warm-boot
    On arm64 the TTBR0_EL1 register is set to either the reserved TTBR0
    page tables on boot or to the active_mm mappings belonging to user space
    processes, it must never be set to swapper_pg_dir page tables mappings.
    When a CPU is booted its active_mm is set to init_mm even though its
    TTBR0_EL1 points at the reserved TTBR0 page mappings. This implies
    that when __cpu_suspend is triggered the active_mm can point at
    init_mm even if the current TTBR0_EL1 register contains the reserved
    TTBR0_EL1 mappings.
    Therefore, the mm save and restore executed in __cpu_suspend might
    turn out to be erroneous in that, if the current->active_mm corresponds
    to init_mm, on resume from low power it ends up restoring in the
    TTBR0_EL1 the init_mm mappings that are global and can cause speculation
    of TLB entries which end up being propagated to user space.
    This patch fixes the issue by checking the active_mm pointer before
    restoring the TTBR0 mappings. If the current active_mm == &init_mm,
    the code sets the TTBR0_EL1 to the reserved TTBR0 mapping instead of
    switching back to the active_mm, which is the expected behaviour
    corresponding to the TTBR0_EL1 settings when __cpu_suspend was entered.
    Fixes: 95322526ef62 ("arm64: kernel: cpu_{suspend/resume} implementation")
    Cc: <stable@xxxxxxxxxxxxxxx> # 3.14+: 18ab7db
    Cc: <stable@xxxxxxxxxxxxxxx> # 3.14+: 714f599
    Cc: <stable@xxxxxxxxxxxxxxx> # 3.14+: c3684fb
    Cc: <stable@xxxxxxxxxxxxxxx> # 3.14+
    Cc: Will Deacon <will.deacon@xxxxxxx>
    Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@xxxxxxx>
    Signed-off-by: Catalin Marinas <catalin.marinas@xxxxxxx>

commit aa39477b5692611b91ac9455ae588738852b3f60
Merge: 48ec833 5164bec
Author: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Date:   Mon Dec 22 14:47:17 2014 -0800

    Merge tag 'dm-3.19-fixes' of 
    Pull device mapper fixes from Mike Snitzer:
     "Thre stable fixes and one fix for a regression introduced during 3.19
       - Fix inability to discard used space when the thin-pool target is in
         out-of-data-space mode and also transition the thin-pool back to
         write mode once free space is made available.
       - Fix DM core bio-based end_io bug that prevented proper
         post-processing of the error code returned from the block layer.
       - Fix crash in DM thin-pool due to thin device being added to the
         pool's active_thins list before properly initializing the thin
         device's refcount"
    * tag 'dm-3.19-fixes' of 
      dm: fix missed error code if .end_io isn't implemented by target_type
      dm thin: fix crash by initializing thin device's refcount and completion 
      dm thin: fix missing out-of-data-space to write mode transition if blocks 
are released
      dm thin: fix inability to discard blocks when in out-of-data-space mode

commit 48ec833b7851438f02164ea846852ce4696f09ad
Author: Kirill A. Shutemov <kirill.shutemov@xxxxxxxxxxxxxxx>
Date:   Mon Dec 22 21:01:54 2014 +0200

    Revert "mm/memory.c: share the i_mmap_rwsem"
    This reverts commit c8475d144abb1e62958cc5ec281d2a9e161c1946.
    There are several[1][2] of bug reports which points to this commit as 
    Let's revert it until we figure out what's going on.
    [1] https://lkml.org/lkml/2014/11/14/342
    [2] https://lkml.org/lkml/2014/12/22/213
    [3] https://lkml.org/lkml/2014/12/9/741
    Signed-off-by: Kirill A. Shutemov <kirill.shutemov@xxxxxxxxxxxxxxx>
    Reported-by: Sasha Levin <sasha.levin@xxxxxxxxxx>
    Acked-by: Davidlohr Bueso <dave@xxxxxxxxxxxx>
    Cc: Hugh Dickins <hughd@xxxxxxxxxx>
    Cc: Oleg Nesterov <oleg@xxxxxxxxxx>
    Cc: Peter Zijlstra (Intel) <peterz@xxxxxxxxxxxxx>
    Cc: Rik van Riel <riel@xxxxxxxxxx>
    Cc: Srikar Dronamraju <srikar@xxxxxxxxxxxxxxxxxx>
    Cc: Mel Gorman <mgorman@xxxxxxx>
    Signed-off-by: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>

commit 31dde116cb084bc0042cafe48975ffb7d1a4ae5d
Author: Catalin Marinas <catalin.marinas@xxxxxxx>
Date:   Thu Dec 18 17:13:49 2014 +0000

    arm64: Replace set_arch_dma_coherent_ops with arch_setup_dma_ops
    Commit a3a60f81ee6f (dma-mapping: replace set_arch_dma_coherent_ops with
    arch_setup_dma_ops) changes the of_dma_configure() arch dma_ops callback
    to arch_setup_dma_ops but only the arch/arm code is updated. Subsequent
    commit 97890ba9289c (dma-mapping: detect and configure IOMMU in
    of_dma_configure) changes the arch_setup_dma_ops() prototype further to
    handle iommu. The patch makes the corresponding arm64 changes.
    Signed-off-by: Catalin Marinas <catalin.marinas@xxxxxxx>
    Reported-by: Arnd Bergmann <arnd@xxxxxxxx>
    Acked-by: Will Deacon <will.deacon@xxxxxxx>

commit 5164bece1673cdf04782f8ed3fba70743700f5da
Author: zhendong chen <alex.chen@xxxxxxxxxx>
Date:   Wed Dec 17 14:37:04 2014 +0800

    dm: fix missed error code if .end_io isn't implemented by target_type
    In bio-based DM's clone_endio(), when target_type doesn't implement
    .end_io (e.g. linear) r will be always be initialized 0.  So if a
    WRITE SAME bio fails WRITE SAME will not be disabled as intended.
    Fix this by initializing r to error, rather than 0, in clone_endio().
    Signed-off-by: Alex Chen <alex.chen@xxxxxxxxxx>
    Signed-off-by: Mike Snitzer <snitzer@xxxxxxxxxx>
    Fixes: 7eee4ae2db ("dm: disable WRITE SAME if it fails")
    Cc: stable@xxxxxxxxxxxxxxx

commit 2b94e8960cc3f225dec058f27570505351f4bc13
Author: Marc Dionne <marc.c.dionne@xxxxxxxxx>
Date:   Wed Dec 17 07:59:59 2014 -0500

    dm thin: fix crash by initializing thin device's refcount and completion 
    Commit 80e96c5484be ("dm thin: do not allow thin device activation
    while pool is suspended") delayed the initialization of a new thin
    device's refcount and completion until after this new thin was added
    to the pool's active_thins list and the pool lock is released.  This
    opens a race with a worker thread that walks the list and calls
    thin_get/put, noticing that the refcount goes to 0 and calling
    complete, freezing up the system and giving the oops below:
     kernel: BUG: unable to handle kernel NULL pointer dereference at           
     kernel: IP: [<ffffffff810d360b>] __wake_up_common+0x2b/0x90
     kernel: Call Trace:
     kernel: [<ffffffff810d3683>] __wake_up_locked+0x13/0x20
     kernel: [<ffffffff810d3dc7>] complete+0x37/0x50
     kernel: [<ffffffffa0595c50>] thin_put+0x20/0x30 [dm_thin_pool]
     kernel: [<ffffffffa059aab7>] do_worker+0x667/0x870 [dm_thin_pool]
     kernel: [<ffffffff816a8a4c>] ? __schedule+0x3ac/0x9a0
     kernel: [<ffffffff810b1aef>] process_one_work+0x14f/0x400
     kernel: [<ffffffff810b206b>] worker_thread+0x6b/0x490
     kernel: [<ffffffff810b2000>] ? rescuer_thread+0x260/0x260
     kernel: [<ffffffff810b6a7b>] kthread+0xdb/0x100
     kernel: [<ffffffff810b69a0>] ? kthread_create_on_node+0x170/0x170
     kernel: [<ffffffff816ad7ec>] ret_from_fork+0x7c/0xb0
     kernel: [<ffffffff810b69a0>] ? kthread_create_on_node+0x170/0x170
    Set the thin device's initial refcount and initialize the completion
    before adding it to the pool's active_thins list in thin_ctr().
    Signed-off-by: Marc Dionne <marc.dionne@xxxxxxxxxxxxxxxxxxxx>
    Signed-off-by: Mike Snitzer <snitzer@xxxxxxxxxx>

commit 2c43fd26e46734430122b8d2ad3024bb532df3ef
Author: Joe Thornber <ejt@xxxxxxxxxx>
Date:   Thu Dec 11 11:12:19 2014 +0000

    dm thin: fix missing out-of-data-space to write mode transition if blocks 
are released
    Discard bios and thin device deletion have the potential to release data
    blocks.  If the thin-pool is in out-of-data-space mode, and blocks were
    released, transition the thin-pool back to full write mode.
    The correct time to do this is just after the thin-pool metadata commit.
    It cannot be done before the commit because the space maps will not
    allow immediate reuse of the data blocks in case there's a rollback
    following power failure.
    Signed-off-by: Joe Thornber <ejt@xxxxxxxxxx>
    Signed-off-by: Mike Snitzer <snitzer@xxxxxxxxxx>
    Cc: stable@xxxxxxxxxxxxxxx

commit 45ec9bd0fd7abf8705e7cf12205ff69fe9d51181
Author: Joe Thornber <ejt@xxxxxxxxxx>
Date:   Wed Dec 10 17:06:57 2014 +0000

    dm thin: fix inability to discard blocks when in out-of-data-space mode
    When the pool was in PM_OUT_OF_SPACE mode its process_prepared_discard
    function pointer was incorrectly being set to
    process_prepared_discard_passdown rather than process_prepared_discard.
    This incorrect function pointer meant the discard was being passed down,
    but not effecting the mapping.  As such any discard that was issued, in
    an attempt to reclaim blocks, would not successfully free data space.
    Reported-by: Eric Sandeen <sandeen@xxxxxxxxxx>
    Signed-off-by: Joe Thornber <ejt@xxxxxxxxxx>
    Signed-off-by: Mike Snitzer <snitzer@xxxxxxxxxx>
    Cc: stable@xxxxxxxxxxxxxxx

Xen-devel mailing list



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