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.11-rc7
Date: Sun, 8 Sep 2024 11:03:02 +0200 [thread overview]
Message-ID: <20240908090302.GAZt1oRk_8H_68AxCe@fat_crate.local> (raw)
Hi Linus,
please pull the locking/urgent lineup for v6.11-rc7.
Thx.
---
The following changes since commit d33d26036a0274b472299d7dcdaa5fb34329f91b:
rtmutex: Drop rt_mutex::wait_lock before scheduling (2024-08-15 15:38:53 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip tags/locking_urgent_for_v6.11_rc7
for you to fetch changes up to de752774f38bb766941ed1bf910ba5a9f6cc6bf7:
jump_label: Fix static_key_slow_dec() yet again (2024-09-06 16:29:22 +0200)
----------------------------------------------------------------
- Correct unwinding the static_call machinery when encountering an error while
loading a module due to a mis-assumption in the static_call_del_module()
path
- Replace a WARN_ON in the memory allocation failure path of the static_call
module machinery which unnecessarily leads to a panic when panic_on_warn is
set
- Fix an ordering problem in jump_label's static key reference counting code
----------------------------------------------------------------
Peter Zijlstra (1):
jump_label: Fix static_key_slow_dec() yet again
Thomas Gleixner (2):
static_call: Handle module init failure correctly in static_call_del_module()
static_call: Replace pointless WARN_ON() in static_call_module_notify()
kernel/jump_label.c | 83 +++++++++++++++++++++++++++++----------------
kernel/static_call_inline.c | 13 ++++++-
2 files changed, 66 insertions(+), 30 deletions(-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next reply other threads:[~2024-09-08 9:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-08 9:03 Borislav Petkov [this message]
2024-09-08 16:41 ` Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2024-09-01 11:43 [GIT pull] irq/urgent " Thomas Gleixner
2024-09-01 11:44 ` [GIT pull] locking/urgent " Thomas Gleixner
2024-09-01 22:04 ` 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=20240908090302.GAZt1oRk_8H_68AxCe@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®