[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250817084235.GAaKGV-7rQHWqTisp3@fat_crate.local>
Date: Sun, 17 Aug 2025 10:42:35 +0200
From: Borislav Petkov <bp@...en8.de>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: x86-ml <x86@...nel.org>, lkml <linux-kernel@...r.kernel.org>
Subject: [GIT PULL] locking/urgent for v6.17-rc2
Hi Linus,
please pull the locking/urgent lineup for v6.17-rc2.
Thx.
---
The following changes since commit e703b7e247503b8bf87b62c02a4392749b09eca8:
futex: Move futex cleanup to __mmdrop() (2025-08-02 15:11:52 +0200)
are available in the Git repository at:
ssh://git@...olite.kernel.org/pub/scm/linux/kernel/git/tip/tip tags/locking_urgent_for_v6.17_rc2
for you to fetch changes up to 21924af67d69d7c9fdaf845be69043cfe75196a1:
locking: Fix __clear_task_blocked_on() warning from __ww_mutex_wound() path (2025-08-13 10:34:54 +0200)
----------------------------------------------------------------
- Make sure sanity checks down in the mutex lock path happen on the correct
type of task so that they don't trigger falsely
- Use the write unsafe user access pairs when writing a futex value to prevent
an error on PowerPC which does user read and write accesses differently
----------------------------------------------------------------
John Stultz (1):
locking: Fix __clear_task_blocked_on() warning from __ww_mutex_wound() path
Waiman Long (1):
futex: Use user_write_access_begin/_end() in futex_put_value()
include/linux/sched.h | 29 +++++++++++++++++------------
kernel/futex/futex.h | 6 +++---
kernel/locking/ww_mutex.h | 6 +++++-
3 files changed, 25 insertions(+), 16 deletions(-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists