1. 03 10月, 2019 3 次提交
  2. 22 6月, 2019 1 次提交
  3. 31 5月, 2019 1 次提交
  4. 30 5月, 2019 1 次提交
  5. 29 5月, 2019 2 次提交
  6. 25 5月, 2019 3 次提交
  7. 04 1月, 2019 1 次提交
    • L
      Remove 'type' argument from access_ok() function · 96d4f267
      Linus Torvalds 提交于
      Nobody has actually used the type (VERIFY_READ vs VERIFY_WRITE) argument
      of the user address range verification function since we got rid of the
      old racy i386-only code to walk page tables by hand.
      
      It existed because the original 80386 would not honor the write protect
      bit when in kernel mode, so you had to do COW by hand before doing any
      user access.  But we haven't supported that in a long time, and these
      days the 'type' argument is a purely historical artifact.
      
      A discussion about extending 'user_access_begin()' to do the range
      checking resulted this patch, because there is no way we're going to
      move the old VERIFY_xyz interface to that model.  And it's best done at
      the end of the merge window when I've done most of my merges, so let's
      just get this done once and for all.
      
      This patch was mostly done with a sed-script, with manual fix-ups for
      the cases that weren't of the trivial 'access_ok(VERIFY_xyz' form.
      
      There were a couple of notable cases:
      
       - csky still had the old "verify_area()" name as an alias.
      
       - the iter_iov code had magical hardcoded knowledge of the actual
         values of VERIFY_{READ,WRITE} (not that they mattered, since nothing
         really used it)
      
       - microblaze used the type argument for a debug printout
      
      but other than those oddities this should be a total no-op patch.
      
      I tried to fix up all architectures, did fairly extensive grepping for
      access_ok() uses, and the changes are trivial, but I may have missed
      something.  Any missed conversion should be trivially fixable, though.
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      96d4f267
  8. 19 12月, 2018 1 次提交
  9. 08 12月, 2018 2 次提交
  10. 06 11月, 2018 2 次提交
  11. 27 9月, 2018 1 次提交
  12. 11 9月, 2018 1 次提交
  13. 15 7月, 2018 1 次提交
  14. 12 7月, 2018 1 次提交
  15. 11 7月, 2018 1 次提交
  16. 24 4月, 2018 3 次提交
  17. 02 5月, 2018 1 次提交
  18. 24 4月, 2018 1 次提交
  19. 11 4月, 2018 2 次提交
  20. 16 3月, 2018 4 次提交
  21. 05 1月, 2018 1 次提交
  22. 28 11月, 2017 1 次提交
  23. 15 11月, 2017 2 次提交
  24. 02 11月, 2017 1 次提交
  25. 28 10月, 2017 1 次提交
    • F
      drm/amdkfd: Clean up kfd_wait_on_events · fdf0c833
      Felix Kuehling 提交于
      Cleaned up the code while resolving some potential bugs and
      inconsistencies in the process.
      
      Clean-ups:
      * Remove enum kfd_event_wait_result, which duplicates
        KFD_IOC_EVENT_RESULT definitions
      * alloc_event_waiters can be called without holding p->event_mutex
      * Return an error code from copy_signaled_event_data instead of bool
      * Clean up error handling code paths to minimize duplication in
        kfd_wait_on_events
      
      Fixes:
      * Consistently return an error code from kfd_wait_on_events and set
        wait_result to KFD_IOC_WAIT_RESULT_FAIL in all failure cases.
      * Always call free_waiters while holding p->event_mutex
      * copy_signaled_event_data might sleep. Don't call it while the task state
        is TASK_INTERRUPTIBLE.
      Signed-off-by: NFelix Kuehling <Felix.Kuehling@amd.com>
      Acked-by: NOded Gabbay <oded.gabbay@gmail.com>
      Signed-off-by: NOded Gabbay <oded.gabbay@gmail.com>
      fdf0c833
  26. 27 9月, 2017 1 次提交