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.8
Date: Mon, 8 Jan 2024 10:12:15 +0100 [thread overview]
Message-ID: <ZZu8bzshIjF689TQ@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-2024-01-08
# HEAD: 2b9d9e0a9ba0e24cb9c78336481f0ed8b2bc1ff2 locking/mutex: Clarify that mutex_unlock(), and most other sleeping locks, can still use the lock object after it's unlocked
Locking changes for v6.8:
- lock guards:
- Use lock guards in the ptrace code
- Introduce conditional guards to extend to conditional lock
primitives like mutex_trylock()/mutex_lock_interruptible()/etc.
- lockdep:
- Optimize 'struct lock_class' to be smaller
- Update file patterns in MAINTAINERS
- mutexes: Document mutex lifetime rules a bit more
Thanks,
Ingo
------------------>
Christophe JAILLET (2):
MAINTAINERS: Add include/linux/lockdep*.h
locking/lockdep: Slightly reorder 'struct lock_class' to save some memory
Ingo Molnar (1):
locking/mutex: Clarify that mutex_unlock(), and most other sleeping locks, can still use the lock object after it's unlocked
Jann Horn (1):
locking/mutex: Document that mutex_unlock() is non-atomic
Peter Zijlstra (2):
cleanup: Add conditional guard support
ptrace: Convert ptrace_attach() to use lock guards
Documentation/locking/mutex-design.rst | 18 ++++
MAINTAINERS | 2 +-
include/linux/cleanup.h | 52 ++++++++++-
include/linux/lockdep_types.h | 2 +-
include/linux/mutex.h | 3 +-
include/linux/rwsem.h | 8 +-
include/linux/sched/task.h | 2 +
include/linux/spinlock.h | 41 +++++++++
kernel/locking/mutex.c | 5 ++
kernel/ptrace.c | 154 ++++++++++++++++-----------------
10 files changed, 197 insertions(+), 90 deletions(-)
next reply other threads:[~2024-01-08 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 9:12 Ingo Molnar [this message]
2024-01-09 4:04 ` [GIT PULL] locking changes for v6.8 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=ZZu8bzshIjF689TQ@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox