1. 15 Oct, 2021 1 commit
    • Michael Ellerman's avatar
      KVM: PPC: Book3S HV: Fix stack handling in idle_kvm_start_guest() · 9b4416c5
      Michael Ellerman authored
      In commit 10d91611 ("powerpc/64s: Reimplement book3s idle code in
      C") kvm_start_guest() became idle_kvm_start_guest(). The old code
      allocated a stack frame on the emergency stack, but didn't use the
      frame to store anything, and also didn't store anything in its caller's
      frame.
      
      idle_kvm_start_guest() on the other hand is written more like a normal C
      function, it creates a frame on entry, and also stores CR/LR into its
      callers frame (per the ABI). The problem is that there is no caller
      frame on the emergency stack.
      
      The emergency stack for a given CPU is allocated with:
      
        paca_ptrs[i]->emergency_sp = alloc_stack(limit, i) + THREAD_SIZE;
      
      So emergency_sp actually points to the first address above the emergency
      stack allocation for a given CPU, we must not store above it without
      first decrementing it to create a frame. This is different to the
      regular kernel stack, paca->kstack, which is initialised to point at an
      initial frame that is ready to use.
      
      idle_kvm_start_guest() stores the backchain, CR and LR all of which
      write outside the allocation for the emergency stack. It then creates a
      stack frame and saves the non-volatile registers. Unfortunately the
      frame it creates is not large enough to fit the non-volatiles, and so
      the saving of the non-volatile registers also writes outside the
      emergency stack allocation.
      
      The end result is that we corrupt whatever is at 0-24 bytes, and 112-248
      bytes above the emergency stack allocation.
      
      In practice this has gone unnoticed because the memory immediately above
      the emergency stack happens to be used for other stack allocations,
      either another CPUs mc_emergency_sp or an IRQ stack. See the order of
      calls to irqstack_early_init() and emergency_stack_init().
      
      The low addresses of another stack are the top of that stack, and so are
      only used if that stack is under extreme pressue, which essentially
      never happens in practice - and if it did there's a high likelyhood we'd
      crash due to that stack overflowing.
      
      Still, we shouldn't be corrupting someone else's stack, and it is purely
      luck that we aren't corrupting something else.
      
      To fix it we save CR/LR into the caller's frame using the existing r1 on
      entry, we then create a SWITCH_FRAME_SIZE frame (which has space for
      pt_regs) on the emergency stack with the backchain pointing to the
      existing stack, and then finally we switch to the new frame on the
      emergency stack.
      
      Fixes: 10d91611 ("powerpc/64s: Reimplement book3s idle code in C")
      Cc: stable@vger.kernel.org # v5.2+
      Signed-off-by: default avatarMichael Ellerman <mpe@ellerman.id.au>
      Link: https://lore.kernel.org/r/20211015133929.832061-1-mpe@ellerman.id.au
      9b4416c5
  2. 13 Oct, 2021 1 commit
  3. 07 Oct, 2021 18 commits
  4. 30 Sep, 2021 1 commit
  5. 20 Sep, 2021 2 commits
    • Linus Torvalds's avatar
      Linux 5.15-rc2 · e4e737bb
      Linus Torvalds authored
      e4e737bb
    • Linus Torvalds's avatar
      pci_iounmap'2: Electric Boogaloo: try to make sense of it all · 316e8d79
      Linus Torvalds authored
      Nathan Chancellor reports that the recent change to pci_iounmap in
      commit 9caea000 ("parisc: Declare pci_iounmap() parisc version only
      when CONFIG_PCI enabled") causes build errors on arm64.
      
      It took me about two hours to convince myself that I think I know what
      the logic of that mess of #ifdef's in the <asm-generic/io.h> header file
      really aim to do, and rewrite it to be easier to follow.
      
      Famous last words.
      
      Anyway, the code has now been lifted from that grotty header file into
      lib/pci_iomap.c, and has fairly extensive comments about what the logic
      is.  It also avoids indirecting through another confusing (and badly
      named) helper function that has other preprocessor config conditionals.
      
      Let's see what odd architecture did something else strange in this area
      to break things.  But my arm64 cross build is clean.
      
      Fixes: 9caea000 ("parisc: Declare pci_iounmap() parisc version only when CONFIG_PCI enabled")
      Reported-by: default avatarNathan Chancellor <nathan@kernel.org>
      Cc: Helge Deller <deller@gmx.de>
      Cc: Arnd Bergmann <arnd@arndb.de>
      Cc: Guenter Roeck <linux@roeck-us.net>
      Cc: Ulrich Teichert <krypton@ulrich-teichert.org>
      Cc: James Bottomley <James.Bottomley@hansenpartnership.com>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      316e8d79
  6. 19 Sep, 2021 17 commits