1. 24 May, 2018 9 commits
  2. 14 May, 2018 12 commits
  3. 13 May, 2018 15 commits
  4. 12 May, 2018 4 commits
    • Linus Torvalds's avatar
      Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux · 427fbe89
      Linus Torvalds authored
      Pull thermal fixes from Zhang Rui:
      
       - fix NULL pointer dereference on module load/probe for int3403_thermal
         driver
      
       - fix an emergency shutdown issue on exynos thermal driver
      
      * 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux:
        thermal: exynos: Propagate error value from tmu_read()
        thermal: exynos: Reading temperature makes sense only when TMU is turned on
        thermal: int3403_thermal: Fix NULL pointer deref on module load / probe
      427fbe89
    • Linus Torvalds's avatar
      Merge tag 'for-linus-20180511' of git://git.kernel.dk/linux-block · 0d4cafd1
      Linus Torvalds authored
      Pull block fixes from Jens Axboe:
       "Just a few NVMe fixes this round - one fixing a use-after-free, one
        fixes the return value after controller reset, and the last one fixes
        an issue where some drives will spuriously EIO. We should get these
        into 4.17"
      
      * tag 'for-linus-20180511' of git://git.kernel.dk/linux-block:
        nvme: add quirk to force medium priority for SQ creation
        nvme: Fix sync controller reset return
        nvme: fix use-after-free in nvme_free_ns_head
      0d4cafd1
    • Jean Delvare's avatar
      swiotlb: silent unwanted warning "buffer is full" · 05e13bb5
      Jean Delvare authored
      If DMA_ATTR_NO_WARN is passed to swiotlb_alloc_buffer(), it should be
      passed further down to swiotlb_tbl_map_single(). Otherwise we escape
      half of the warnings but still log the other half.
      
      This is one of the multiple causes of spurious warnings reported at:
      https://bugs.freedesktop.org/show_bug.cgi?id=104082Signed-off-by: default avatarJean Delvare <jdelvare@suse.de>
      Fixes: 0176adb0 ("swiotlb: refactor coherent buffer allocation")
      Cc: Christoph Hellwig <hch@lst.de>
      Cc: Christian König <christian.koenig@amd.com>
      Cc: Michel Dänzer <michel@daenzer.net>
      Cc: Takashi Iwai <tiwai@suse.de>
      Cc: stable@vger.kernel.org # v4.16
      05e13bb5
    • Mel Gorman's avatar
      Revert "sched/numa: Delay retrying placement for automatic NUMA balance after wake_affine()" · 789ba280
      Mel Gorman authored
      This reverts commit 7347fc87.
      
      Srikar Dronamra pointed out that while the commit in question did show
      a performance improvement on ppc64, it did so at the cost of disabling
      active CPU migration by automatic NUMA balancing which was not the intent.
      The issue was that a serious flaw in the logic failed to ever active balance
      if SD_WAKE_AFFINE was disabled on scheduler domains. Even when it's enabled,
      the logic is still bizarre and against the original intent.
      
      Investigation showed that fixing the patch in either the way he suggested,
      using the correct comparison for jiffies values or introducing a new
      numa_migrate_deferred variable in task_struct all perform similarly to a
      revert with a mix of gains and losses depending on the workload, machine
      and socket count.
      
      The original intent of the commit was to handle a problem whereby
      wake_affine, idle balancing and automatic NUMA balancing disagree on the
      appropriate placement for a task. This was particularly true for cases where
      a single task was a massive waker of tasks but where wake_wide logic did
      not apply.  This was particularly noticeable when a futex (a barrier) woke
      all worker threads and tried pulling the wakees to the waker nodes. In that
      specific case, it could be handled by tuning MPI or openMP appropriately,
      but the behavior is not illogical and was worth attempting to fix. However,
      the approach was wrong. Given that we're at rc4 and a fix is not obvious,
      it's better to play safe, revert this commit and retry later.
      Signed-off-by: default avatarMel Gorman <mgorman@techsingularity.net>
      Signed-off-by: default avatarPeter Zijlstra (Intel) <peterz@infradead.org>
      Reviewed-by: default avatarSrikar Dronamraju <srikar@linux.vnet.ibm.com>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: efault@gmx.de
      Cc: ggherdovich@suse.cz
      Cc: hpa@zytor.com
      Cc: matt@codeblueprint.co.uk
      Cc: mpe@ellerman.id.au
      Link: http://lkml.kernel.org/r/20180509163115.6fnnyeg4vdm2ct4v@techsingularity.netSigned-off-by: default avatarIngo Molnar <mingo@kernel.org>
      789ba280