From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] locking/urgent for v6.2-rc2
Date: Sun, 1 Jan 2023 15:59:55 +0100 [thread overview]
Message-ID: <Y7Gf65Z5S++WefTw@zn.tnic> (raw)
Hi Linus,
please pull a couple of urgent locking fixes for 6.2.
Thx.
---
The following changes since commit 830b3c68c1fb1e9176028d02ef86f3cf76aa2476:
Linux 6.1 (2022-12-11 14:15:18 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/locking_urgent_for_v6.2_rc2
for you to fetch changes up to 94cd8fa09f5f1ebdd4e90964b08b7f2cc4b36c43:
futex: Fix futex_waitv() hrtimer debug object leak on kcalloc error (2022-12-27 12:52:02 +0100)
----------------------------------------------------------------
- Prevent the leaking of a debug timer in futex_waitv()
- A preempt-RT mutex locking fix, adding the proper acquire semantics
----------------------------------------------------------------
Mathieu Desnoyers (1):
futex: Fix futex_waitv() hrtimer debug object leak on kcalloc error
Mel Gorman (1):
rtmutex: Add acquire semantics for rtmutex lock acquisition slow path
kernel/futex/syscalls.c | 11 +++++----
kernel/locking/rtmutex.c | 55 ++++++++++++++++++++++++++++++++++++--------
kernel/locking/rtmutex_api.c | 6 ++---
3 files changed, 56 insertions(+), 16 deletions(-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next reply other threads:[~2023-01-01 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-01 14:59 Borislav Petkov [this message]
2023-01-01 19:30 ` [GIT PULL] locking/urgent for v6.2-rc2 pr-tracker-bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y7Gf65Z5S++WefTw@zn.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox