From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Will Deacon <will@kernel.org>, Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] Locking updates for v6.0
Date: Mon, 1 Aug 2022 16:11:11 +0200 [thread overview]
Message-ID: <Yufe/3UMD2f4WFZK@gmail.com> (raw)
Linus,
Please pull the latest locking/core git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking-core-2022-08-01
# HEAD: eae6d58d67d9739be5f7ae2dbead1d0ef6528243 locking/lockdep: Fix lockdep_init_map_*() confusion
This was a fairly quiet cycle for the locking subsystem:
- lockdep: Fix a handful of the more complex lockdep_init_map_*() primitives
that can lose the lock_type & cause false reports. No such mishap was
observed in the wild.
- jump_label improvements: simplify the cross-arch support of
initial NOP patching by making it arch-specific code (used on MIPS only),
and remove the s390 initial NOP patching that was superfluous.
Thanks,
Ingo
------------------>
Ard Biesheuvel (3):
jump_label: s390: avoid pointless initial NOP patching
jump_label: mips: move module NOP patching into arch code
jump_label: make initial NOP patching the special case
Peter Zijlstra (1):
locking/lockdep: Fix lockdep_init_map_*() confusion
Documentation/staging/static-keys.rst | 3 ---
arch/arc/kernel/jump_label.c | 13 -----------
arch/arm/kernel/jump_label.c | 6 -----
arch/arm64/kernel/jump_label.c | 11 ----------
arch/mips/include/asm/jump_label.h | 2 ++
arch/mips/kernel/jump_label.c | 19 ++++++++++++++++
arch/mips/kernel/module.c | 5 +++--
arch/parisc/kernel/jump_label.c | 11 ----------
arch/riscv/kernel/jump_label.c | 12 ----------
arch/s390/include/asm/jump_label.h | 5 ++---
arch/s390/kernel/jump_label.c | 28 +++++-------------------
arch/s390/kernel/module.c | 1 -
arch/sparc/kernel/module.c | 3 ---
arch/x86/kernel/jump_label.c | 13 -----------
arch/x86/kernel/module.c | 3 ---
include/linux/jump_label.h | 9 +-------
include/linux/lockdep.h | 30 ++++++++++++++-----------
kernel/jump_label.c | 41 +++++------------------------------
kernel/locking/lockdep.c | 7 +++---
19 files changed, 59 insertions(+), 163 deletions(-)
next reply other threads:[~2022-08-01 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 14:11 Ingo Molnar [this message]
2022-08-01 19:55 ` [GIT PULL] Locking updates for v6.0 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=Yufe/3UMD2f4WFZK@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=boqun.feng@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox