1. 02 7月, 2014 2 次提交
  2. 01 7月, 2014 2 次提交
    • U
      ARM: make user_addr_max more robust · 83de911c
      Uwe Kleine-König 提交于
      With CONFIG_MMU=y get_fs() returns current_thread_info()->addr_limit
      which is initialized as USER_DS (which in turn is defined to TASK_SIZE)
      for userspace processes. At least theoretically
      current_thread_info()->addr_limit is changable by set_fs() to a
      different limit, so checking for KERNEL_DS is more robust.
      
      With !CONFIG_MMU get_fs returns KERNEL_DS. To see what the old variant
      did you'd have to find out that USER_DS == KERNEL_DS which isn't needed
      any more with the variant this patch introduces. So it's a bit easier to
      understand, too.
      
      Also if the limit was changed this limit should be returned, not
      TASK_SIZE.
      Signed-off-by: NUwe Kleine-König <u.kleine-koenig@pengutronix.de>
      83de911c
    • U
      ARM: nommu: don't limit TASK_SIZE · 03eca200
      Uwe Kleine-König 提交于
      With TASK_SIZE set to the maximal RAM address booting in some XIP
      configurations fails (e.g. on efm32 DK3750). The problem is that
      strncpy_from_user et al. check for the address not being above TASK_SIZE
      (since 8c56cc8b (ARM: 7449/1: use generic strnlen_user and
      strncpy_from_user functions)) and this makes booting fail if the XIP
      flash is above the RAM address space.
      
      This change is in line with blackfin, frv and m68k which also use
      0xffffffff for TASK_SIZE with !MMU.
      Signed-off-by: NUwe Kleine-König <u.kleine-koenig@pengutronix.de>
      03eca200
  3. 29 6月, 2014 1 次提交
  4. 18 6月, 2014 1 次提交
  5. 17 6月, 2014 1 次提交
  6. 08 6月, 2014 1 次提交
  7. 02 6月, 2014 2 次提交
  8. 01 6月, 2014 2 次提交
  9. 30 5月, 2014 10 次提交
  10. 29 5月, 2014 1 次提交
  11. 28 5月, 2014 1 次提交
  12. 27 5月, 2014 1 次提交
  13. 26 5月, 2014 6 次提交
  14. 24 5月, 2014 1 次提交
  15. 22 5月, 2014 4 次提交
  16. 21 5月, 2014 1 次提交
  17. 20 5月, 2014 1 次提交
  18. 15 5月, 2014 1 次提交
  19. 13 5月, 2014 1 次提交