1. 07 Aug, 2018 2 commits
  2. 01 Aug, 2018 1 commit
    • Martin Schwidefsky's avatar
      s390/numa: move initial setup of node_to_cpumask_map · fb7d7518
      Martin Schwidefsky authored
      The numa_init_early initcall sets the node_to_cpumask_map[0] to the
      full cpu_possible_mask. Unfortunately this early_initcall is too late,
      the NUMA setup for numa=emu is done even earlier. The order of calls
      is numa_setup() -> emu_update_cpu_topology(), then the early_initcalls(),
      followed by sched_init_domains().
      
      Starting with git commit 051f3ca0
      "sched/topology: Introduce NUMA identity node sched domain"
      the incorrect node_to_cpumask_map[0] really screws up the domain
      setup and the kernel panics with the follow oops:
      
      Cc: <stable@vger.kernel.org> # v4.15+
      Signed-off-by: default avatarMartin Schwidefsky <schwidefsky@de.ibm.com>
      fb7d7518
  3. 31 Jul, 2018 3 commits
  4. 30 Jul, 2018 13 commits
  5. 25 Jul, 2018 2 commits
    • Martin Schwidefsky's avatar
      s390: reenable gcc plugins · 6eedfaac
      Martin Schwidefsky authored
      Now that the early boot rework is upstream we can enable the gcc plugins
      again. See git commit 72f108b308707f21499e0ac05bf7370360cf06d8
      "s390: disable gcc plugins" for reference.
      Signed-off-by: default avatarMartin Schwidefsky <schwidefsky@de.ibm.com>
      6eedfaac
    • Martin Schwidefsky's avatar
      s390: disable gcc plugins · 2a6777a1
      Martin Schwidefsky authored
      The s390 build currently fails with the latent entropy plugin:
      
      arch/s390/kernel/als.o: In function `verify_facilities':
      als.c:(.init.text+0x24): undefined reference to `latent_entropy'
      als.c:(.init.text+0xae): undefined reference to `latent_entropy'
      make[3]: *** [arch/s390/boot/compressed/vmlinux] Error 1
      make[2]: *** [arch/s390/boot/compressed/vmlinux] Error 2
      make[1]: *** [bzImage] Error 2
      
      This will be fixed with the early boot rework from Vasily, which
      is planned for the 4.19 merge window.
      
      For 4.18 the simplest solution is to disable the gcc plugins and
      reenable them after the early boot rework is upstream.
      Reported-by: default avatarGuenter Roeck <linux@roeck-us.net>
      Signed-off-by: default avatarMartin Schwidefsky <schwidefsky@de.ibm.com>
      (cherry picked from commit 2fba3573)
      2a6777a1
  6. 23 Jul, 2018 7 commits
  7. 19 Jul, 2018 5 commits
  8. 18 Jul, 2018 1 commit
  9. 17 Jul, 2018 5 commits
  10. 16 Jul, 2018 1 commit
    • Claudio Imbrenda's avatar
      s390/kvm: fix deadlock when killed by oom · 306d6c49
      Claudio Imbrenda authored
      When the oom killer kills a userspace process in the page fault handler
      while in guest context, the fault handler fails to release the mm_sem
      if the FAULT_FLAG_RETRY_NOWAIT option is set. This leads to a deadlock
      when tearing down the mm when the process terminates. This bug can only
      happen when pfault is enabled, so only KVM clients are affected.
      
      The problem arises in the rare cases in which handle_mm_fault does not
      release the mm_sem. This patch fixes the issue by manually releasing
      the mm_sem when needed.
      
      Fixes: 24eb3a82 ("KVM: s390: Add FAULT_FLAG_RETRY_NOWAIT for guest fault")
      Cc: <stable@vger.kernel.org> # 3.15+
      Signed-off-by: default avatarClaudio Imbrenda <imbrenda@linux.vnet.ibm.com>
      Signed-off-by: default avatarMartin Schwidefsky <schwidefsky@de.ibm.com>
      306d6c49