diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2021-05-09 13:07:03 -0700 | 
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2021-05-09 13:07:03 -0700 | 
| commit | 732a27a0891cb5db1a0f9c33a018ea6eca9a4023 (patch) | |
| tree | 35d7ee5c21df90cb66c6734e11a777f1be3df66d /lib/zstd/common/debug.c | |
| parent | 85bbba1c077848e76ab77682e9e56c41113f5770 (diff) | |
| parent | 51cf94d16860a324e97d1b670d88f1f2b643bc32 (diff) | |
Merge tag 'locking-urgent-2021-05-09' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull locking fixes from Thomas Gleixner:
 "A set of locking related fixes and updates:
   - Two fixes for the futex syscall related to the timeout handling.
     FUTEX_LOCK_PI does not support the FUTEX_CLOCK_REALTIME bit and
     because it's not set the time namespace adjustment for clock
     MONOTONIC is applied wrongly.
     FUTEX_WAIT cannot support the FUTEX_CLOCK_REALTIME bit because its
     always a relative timeout.
   - Cleanups in the futex syscall entry points which became obvious
     when the two timeout handling bugs were fixed.
   - Cleanup of queued_write_lock_slowpath() as suggested by Linus
   - Fixup of the smp_call_function_single_async() prototype"
* tag 'locking-urgent-2021-05-09' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
  futex: Make syscall entry points less convoluted
  futex: Get rid of the val2 conditional dance
  futex: Do not apply time namespace adjustment on FUTEX_LOCK_PI
  Revert 337f13046ff0 ("futex: Allow FUTEX_CLOCK_REALTIME with FUTEX_WAIT op")
  locking/qrwlock: Cleanup queued_write_lock_slowpath()
  smp: Fix smp_call_function_single_async prototype
Diffstat (limited to 'lib/zstd/common/debug.c')
0 files changed, 0 insertions, 0 deletions
