From: Boqun Feng <boqun.feng@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>, mingo@redhat.com
Cc: "Will Deacon" <will@kernel.org>,
"Waiman Long" <longman@redhat.com>,
linux-kernel@vger.kernel.org, "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
rust-for-linux@vger.kernel.org
Subject: Re: [GIT PULL] LOCKDEP and Rust locking changes for v6.15
Date: Fri, 28 Feb 2025 10:57:37 -0800 [thread overview]
Message-ID: <Z8IHIYOnI-DMHlC8@boqun-archlinux> (raw)
In-Reply-To: <Z76Uk1d4SHPwVD6n@Mac.home>
On Tue, Feb 25, 2025 at 08:12:03PM -0800, Boqun Feng wrote:
> Hi Peter & Ingo,
>
Ping ;-)
Regards,
Boqun
> Please pull the changes of lockdep and Rust locking for v6.15 into tip.
>
> The following changes since commit 337369f8ce9e20226402cf139c4f0d3ada7d1705:
>
> locking/mutex: Add MUTEX_WARN_ON() into fast path (2025-02-21 20:19:12 +0100)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/boqun/linux.git tags/lockdep-for-tip.2025.02.25
>
> for you to fetch changes up to 3b5b307cf84ca3a73abe797df31e0efe897411a9:
>
> rust: lockdep: Use Pin for all LockClassKey usages (2025-02-25 08:53:08 -0800)
>
>
> Regards,
> Boqun
>
> ----------------------------------------------------------------
> Lockdep changes for v6.15:
>
> - Fix kernel-doc for rtmutex.
> - Fix lock wait context check on softirq for PREEMPT_RT.
> - Disable KASAN for lockdep to improve debug kernel performance.
>
> Miscellaneous locking changes for v6.15:
>
> - Use wake_q for semaphore to avoid wake-up in lock critical sections.
>
> Rust locking changes for v6.15:
>
> - Fix the soundness issue around dynamically allocated lock class keys.
> - Add CondVar::wait_interruptible_freezable() to allow freezable waits.
> - Add Guard::lock_ref() to access the lock reference behind a lock
> guard.
>
> ----------------------------------------------------------------
> Alice Ryhl (2):
> rust: sync: Add accessor for the lock behind a given guard
> rust: sync: condvar: Add wait_interruptible_freezable()
>
> Boqun Feng (1):
> rust: sync: lock: Add an example for Guard::lock_ref()
>
> Mitchell Levy (2):
> rust: lockdep: Remove support for dynamically allocated LockClassKeys
> rust: lockdep: Use Pin for all LockClassKey usages
>
> Randy Dunlap (1):
> locking/rtmutex: Use struct keyword in kernel-doc comment
>
> Ryo Takakura (1):
> lockdep: Fix wait context check on softirq for PREEMPT_RT
>
> Waiman Long (5):
> locking/semaphore: Use wake_q to wake up processes outside lock critical section
> locking/lock_events: Add locking events for rtmutex slow paths
> locking/lock_events: Add locking events for lockdep
> locking/lockdep: Disable KASAN instrumentation of lockdep.c
> locking/lockdep: Add kasan_check_byte() check in lock_acquire()
>
> include/linux/bottom_half.h | 8 +++++
> kernel/locking/Makefile | 3 +-
> kernel/locking/lock_events_list.h | 28 +++++++++++++++++
> kernel/locking/lockdep.c | 17 ++++++++++-
> kernel/locking/rtmutex.c | 29 ++++++++++++++----
> kernel/locking/rtmutex_common.h | 4 +--
> kernel/locking/semaphore.c | 13 +++++---
> kernel/softirq.c | 12 ++++++++
> rust/helpers/helpers.c | 1 +
> rust/helpers/sync.c | 13 ++++++++
> rust/kernel/sync.rs | 63 ++++++++++++++++++++++++++++++++-------
> rust/kernel/sync/condvar.rs | 28 ++++++++++++++---
> rust/kernel/sync/lock.rs | 35 ++++++++++++++++++++--
> rust/kernel/sync/lock/global.rs | 5 ++--
> rust/kernel/sync/poll.rs | 2 +-
> rust/kernel/task.rs | 2 ++
> rust/kernel/workqueue.rs | 2 +-
> 17 files changed, 231 insertions(+), 34 deletions(-)
> create mode 100644 rust/helpers/sync.c
next prev parent reply other threads:[~2025-02-28 18:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 4:12 [GIT PULL] LOCKDEP and Rust locking changes for v6.15 Boqun Feng
2025-02-28 18:57 ` Boqun Feng [this message]
2025-03-03 16:52 ` Waiman Long
2025-03-03 18:42 ` Peter Zijlstra
2025-03-07 23:26 ` [PATCH locking 00/11] " Boqun Feng
2025-03-07 23:26 ` [PATCH locking 07/11] rust: sync: Add accessor for the lock behind a given guard Boqun Feng
2025-03-07 23:26 ` [PATCH locking 08/11] rust: sync: lock: Add an example for Guard::lock_ref() Boqun Feng
2025-03-07 23:26 ` [PATCH locking 09/11] rust: sync: condvar: Add wait_interruptible_freezable() Boqun Feng
2025-03-07 23:27 ` [PATCH locking 10/11] rust: lockdep: Remove support for dynamically allocated LockClassKeys Boqun Feng
2025-03-07 23:27 ` [PATCH locking 11/11] rust: lockdep: Use Pin for all LockClassKey usages Boqun Feng
2025-03-08 0:01 ` [PATCH locking 00/11] LOCKDEP and Rust locking changes for v6.15 Ingo Molnar
2025-03-08 0:04 ` Boqun Feng
2025-03-08 0:11 ` Ingo Molnar
2025-03-08 0:11 ` Boqun Feng
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=Z8IHIYOnI-DMHlC8@boqun-archlinux \
--to=boqun.feng@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--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;
as well as URLs for NNTP newsgroup(s).