1. 13 10月, 2017 11 次提交
  2. 22 9月, 2017 4 次提交
  3. 20 9月, 2017 2 次提交
  4. 09 9月, 2017 2 次提交
  5. 05 9月, 2017 1 次提交
  6. 04 9月, 2017 2 次提交
  7. 02 9月, 2017 2 次提交
  8. 01 9月, 2017 2 次提交
  9. 31 8月, 2017 5 次提交
  10. 29 8月, 2017 2 次提交
    • M
      ARM: 8692/1: mm: abort uaccess retries upon fatal signal · 746a272e
      Mark Rutland 提交于
      When there's a fatal signal pending, arm's do_page_fault()
      implementation returns 0. The intent is that we'll return to the
      faulting userspace instruction, delivering the signal on the way.
      
      However, if we take a fatal signal during fixing up a uaccess, this
      results in a return to the faulting kernel instruction, which will be
      instantly retried, resulting in the same fault being taken forever. As
      the task never reaches userspace, the signal is not delivered, and the
      task is left unkillable. While the task is stuck in this state, it can
      inhibit the forward progress of the system.
      
      To avoid this, we must ensure that when a fatal signal is pending, we
      apply any necessary fixup for a faulting kernel instruction. Thus we
      will return to an error path, and it is up to that code to make forward
      progress towards delivering the fatal signal.
      Signed-off-by: NMark Rutland <mark.rutland@arm.com>
      Reviewed-by: NSteve Capper <steve.capper@arm.com>
      Cc: stable@vger.kernel.org
      Signed-off-by: NRussell King <rmk+kernel@armlinux.org.uk>
      746a272e
    • H
      ARM: 8690/1: lpae: build TTB control register value from scratch in v7_ttb_setup · f26fee5f
      Hoeun Ryu 提交于
      Reading TTBCR in early boot stage might return the value of the previous
      kernel's configuration, especially in case of kexec. For example, if
      normal kernel (first kernel) had run on a configuration of PHYS_OFFSET <=
      PAGE_OFFSET and crash kernel (second kernel) is running on a configuration
      PHYS_OFFSET > PAGE_OFFSET, which can happen because it depends on the
      reserved area for crash kernel, reading TTBCR and using the value to OR
      other bit fields might be risky because it doesn't have a reset value for TTBCR.
      Suggested-by: NRobin Murphy <robin.murphy@arm.com>
      Signed-off-by: NHoeun Ryu <hoeun.ryu@gmail.com>
      Signed-off-by: NRussell King <rmk+kernel@armlinux.org.uk>
      f26fee5f
  11. 28 8月, 2017 6 次提交
  12. 27 8月, 2017 1 次提交