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.17-rc1
Date: Sat, 9 Aug 2025 20:02:07 +0200 [thread overview]
Message-ID: <20250809180207.GAaJeNHymvt6gaR5nY@fat_crate.local> (raw)
Hi Linus,
please pull a locking/urgent fix for v6.17-rc1.
Thx.
---
The following changes since commit 98e8f2c0e0930feee6a2538450c74d9d7de0a9cc:
Merge tag 'x86-platform-2025-07-29' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2025-07-29 20:05:06 -0700)
are available in the Git repository at:
ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/tip/tip tags/locking_urgent_for_v6.17_rc1
for you to fetch changes up to e703b7e247503b8bf87b62c02a4392749b09eca8:
futex: Move futex cleanup to __mmdrop() (2025-08-02 15:11:52 +0200)
----------------------------------------------------------------
- Prevent a futex hash leak due to different mm lifetimes
----------------------------------------------------------------
Thomas Gleixner (1):
futex: Move futex cleanup to __mmdrop()
kernel/fork.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next reply other threads:[~2025-08-09 18:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-09 18:02 Borislav Petkov [this message]
2025-08-10 5:58 ` pr-tracker-bot
2025-08-21 18:19 ` Linus Torvalds
2025-08-21 19:45 ` Sean Christopherson
2025-08-22 14:16 ` Sebastian Andrzej Siewior
2025-08-23 0:28 ` Sean Christopherson
2025-08-25 16:04 ` Sebastian Andrzej Siewior
2025-08-25 23:55 ` Sean Christopherson
2025-08-22 10:57 ` Sebastian Andrzej Siewior
2025-08-22 14:12 ` [PATCH] futex: Move futex_hash_free() back to __mmput() Sebastian Andrzej Siewior
2025-08-27 11:34 ` [tip: locking/urgent] " tip-bot2 for Sebastian Andrzej Siewior
2025-08-31 12:23 ` tip-bot2 for Sebastian Andrzej Siewior
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=20250809180207.GAaJeNHymvt6gaR5nY@fat_crate.local \
--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
all inboxes | Powered by JetHome®