From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Will Deacon <will@kernel.org>, Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>, Borislav Petkov <bp@alien8.de>
Subject: [GIT PULL] locking changes for v6.12
Date: Sun, 29 Sep 2024 09:10:33 +0200 [thread overview]
Message-ID: <Zvj9aYsNdWNGJbed@gmail.com> (raw)
Linus,
Please pull the latest locking/urgent Git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking-urgent-2024-09-29
# HEAD: ae39e0bd150bd2739582f72ad70b5a0b15e74576 Merge branch 'locking/core' into locking/urgent, to pick up pending commits
Locking changes for v6.12:
- lockdep:
- Fix potential deadlock between lockdep and RCU (Zhiguo Niu)
- Use str_plural() to address Coccinelle warning (Thorsten Blum)
- Add debuggability enhancement (Luis Claudio R. Goncalves)
- static keys & calls:
- Fix static_key_slow_dec() yet again (Peter Zijlstra)
- Handle module init failure correctly in static_call_del_module() (Thomas Gleixner)
- Replace pointless WARN_ON() in static_call_module_notify() (Thomas Gleixner)
- <linux/cleanup.h>:
- Add usage and style documentation (Dan Williams)
- rwsems:
- Move is_rwsem_reader_owned() and rwsem_owner() under CONFIG_DEBUG_RWSEMS (Waiman Long)
- atomic ops, x86:
- Redeclare x86_32 arch_atomic64_{add,sub}() as void (Uros Bizjak)
- Introduce the read64_nonatomic macro to x86_32 with cx8 (Uros Bizjak)
Thanks,
Ingo
------------------>
Dan Williams (1):
cleanup: Add usage and style documentation
Luis Claudio R. Goncalves (1):
lockdep: suggest the fix for "lockdep bfs error:-1" on print_bfs_bug
Markus Elfring (1):
locking/lockdep: Simplify character output in seq_line()
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()
Thorsten Blum (1):
lockdep: Use str_plural() to fix Coccinelle warning
Uros Bizjak (2):
locking/atomic/x86: Introduce the read64_nonatomic macro to x86_32 with cx8
locking/atomic/x86: Redeclare x86_32 arch_atomic64_{add,sub}() as void
Waiman Long (1):
locking/rwsem: Move is_rwsem_reader_owned() and rwsem_owner() under CONFIG_DEBUG_RWSEMS
Zhiguo Niu (1):
lockdep: fix deadlock issue between lockdep and rcu
Documentation/core-api/cleanup.rst | 8 +++
Documentation/core-api/index.rst | 1 +
arch/x86/include/asm/atomic64_32.h | 6 +-
arch/x86/lib/atomic64_cx8_32.S | 9 ++-
include/linux/cleanup.h | 136 +++++++++++++++++++++++++++++++++++++
kernel/jump_label.c | 34 ++++++++--
kernel/locking/lockdep.c | 55 ++++++++++-----
kernel/locking/lockdep_proc.c | 2 +-
kernel/locking/rwsem.c | 22 +++---
kernel/static_call_inline.c | 13 +++-
10 files changed, 241 insertions(+), 45 deletions(-)
create mode 100644 Documentation/core-api/cleanup.rst
next reply other threads:[~2024-09-29 7:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 7:10 Ingo Molnar [this message]
2024-09-29 17:05 ` [GIT PULL] locking changes for v6.12 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=Zvj9aYsNdWNGJbed@gmail.com \
--to=mingo@kernel.org \
--cc=boqun.feng@gmail.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=will@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.