summaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/xarray.py
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2025-07-20 21:22:05 +0300
committerLinus Torvalds <torvalds@linux-foundation.org>2025-07-20 21:22:05 +0300
commit92329d578d60fe944e30da287ee28f5c154a5802 (patch)
treee64d1f8116622d8d3c7ab5d5b503fae1b3edd554 /scripts/gdb/linux/xarray.py
parent62347e279092ae704877467abdc8533e914f945e (diff)
parentd0a48dc4df5c986bf8c3caf4d8fc15c480273052 (diff)
downloadlinux-92329d578d60fe944e30da287ee28f5c154a5802.tar.xz
Merge tag 'locking-urgent-2025-07-20' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull locking fix from Thomas Gleixner: "A single fix for the futex selftest code to make 32-bit user space work correctly on 64-bit kernels. sys_futex_wait() expects a struct __kernel_timespec for the timeout, but the selftest uses struct timespec, which is the original 32-bit non 2038 compliant variant. Fix it up by converting the callsite supplied timespec to a __kernel_timespec and hand that into the syscall" * tag 'locking-urgent-2025-07-20' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: selftests/futex: Convert 32-bit timespec to 64-bit version for 32-bit compatibility mode
Diffstat (limited to 'scripts/gdb/linux/xarray.py')
0 files changed, 0 insertions, 0 deletions