1. 06 Jul, 2015 35 commits
  2. 02 Jul, 2015 2 commits
    • Doug Ledford's avatar
      IB/ipoib: change init sequence ordering · 32eb7ef5
      Doug Ledford authored
      commit be7aa663 upstream.
      
      In preparation for using per device work queues, we need to move the
      start of the neighbor thread task to after ipoib_ib_dev_init and move
      the destruction of the neighbor task to before ipoib_ib_dev_cleanup.
      Otherwise we will end up freeing our workqueue with work possibly
      still on it.
      Signed-off-by: default avatarDoug Ledford <dledford@redhat.com>
      Cc: Joseph Salisbury <joseph.salisbury@canonical.com>
      Signed-off-by: default avatarKamal Mostafa <kamal@canonical.com>
      32eb7ef5
    • Doug Ledford's avatar
      IB/ipoib: factor out ah flushing · 7294ca57
      Doug Ledford authored
      commit e135106f upstream.
      
      Create a an ipoib_flush_ah and ipoib_stop_ah routines to use at
      appropriate times to flush out all remaining ah entries before we shut
      the device down.
      
      Because neighbors and mcast entries can each have a reference on any
      given ah, we must make sure to free all of those first before our ah
      will actually have a 0 refcount and be able to be reaped.
      
      This factoring is needed in preparation for having per-device work
      queues.  The original per-device workqueue code resulted in the following
      error message:
      
      <ibdev>: ib_dealloc_pd failed
      
      That error was tracked down to this issue.  With the changes to which
      workqueues were flushed when, there were no flushes of the per device
      workqueue after the last ah's were freed, resulting in an attempt to
      dealloc the pd with outstanding resources still allocated.  This code
      puts the explicit flushes in the needed places to avoid that problem.
      Signed-off-by: default avatarDoug Ledford <dledford@redhat.com>
      Cc: Joseph Salisbury <joseph.salisbury@canonical.com>
      Signed-off-by: default avatarKamal Mostafa <kamal@canonical.com>
      7294ca57
  3. 30 Jun, 2015 3 commits
    • Paolo Bonzini's avatar
      kvm: x86: fix kvm_apic_has_events to check for NULL pointer · 23caff1e
      Paolo Bonzini authored
      commit ce40cd3f upstream.
      
      Malicious (or egregiously buggy) userspace can trigger it, but it
      should never happen in normal operation.
      Signed-off-by: default avatarPaolo Bonzini <pbonzini@redhat.com>
      Reference: CVE-2015-4692
      Signed-off-by: default avatarKamal Mostafa <kamal@canonical.com>
      23caff1e
    • Ingo Molnar's avatar
      x86/fpu: Disable XSAVES* support for now · e392edcd
      Ingo Molnar authored
      commit e88221c5 upstream.
      
      The kernel's handling of 'compacted' xsave state layout is buggy:
      
          http://marc.info/?l=linux-kernel&m=142967852317199
      
      I don't have such a system, and the description there is vague, but
      from extrapolation I guess that there were two kinds of bugs
      observed:
      
        - boot crashes, due to size calculations being wrong and the dynamic
          allocation allocating a too small xstate area. (This is now fixed
          in the new FPU code - but still present in stable kernels.)
      
        - FPU state corruption and ABI breakage: if signal handlers try to
          change the FPU state in standard format, which then the kernel
          tries to restore in the compacted format.
      
      These breakages are scary, but they only occur on a small number of
      systems that have XSAVES* CPU support. Yet we have had XSAVES support
      in the upstream kernel for a large number of stable kernel releases,
      and the fixes are involved and unproven.
      
      So do the safe resolution first: disable XSAVES* support and only
      use the standard xstate format. This makes the code work and is
      easy to backport.
      
      On top of this we can work on enabling (and testing!) proper
      compacted format support, without backporting pressure, on top of the
      new, cleaned up FPU code.
      
      Cc: Andy Lutomirski <luto@amacapital.net>
      Cc: Borislav Petkov <bp@alien8.de>
      Cc: Dave Hansen <dave.hansen@linux.intel.com>
      Cc: Fenghua Yu <fenghua.yu@intel.com>
      Cc: H. Peter Anvin <hpa@zytor.com>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Cc: Oleg Nesterov <oleg@redhat.com>
      Cc: Peter Zijlstra <peterz@infradead.org>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Signed-off-by: default avatarIngo Molnar <mingo@kernel.org>
      Cc: Timo Aaltonen <timo.aaltonen@canonical.com>
      Signed-off-by: default avatarKamal Mostafa <kamal@canonical.com>
      e392edcd
    • Kamal Mostafa's avatar
      Revert "tools/vm: fix page-flags build" · 1dcf99c1
      Kamal Mostafa authored
      This reverts commit 3ddd7003
      from 3.19-stable.
      
      Patch is not suitable for 3.19-stable (breaks "make -C tools/vm").
      
      Cc: Sasha Levin <sasha.levin@oracle.com>
      Signed-off-by: default avatarKamal Mostafa <kamal@canonical.com>
      1dcf99c1