Rust for Linux List
 help / color / mirror / Atom feed
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>,
	"Boqun Feng" <boqun.feng@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>,
	rust-for-linux@vger.kernel.org, "Lyude Paul" <lyude@redhat.com>
Subject: [GIT PULL] LOCKDEP and Rust locking changes for v6.14
Date: Fri, 20 Dec 2024 16:00:59 -0800	[thread overview]
Message-ID: <Z2YFO5zr9vm5kdjb@tardis.local> (raw)

Hi Peter & Ingo,

Please pull the changes of lockdep and Rust locking for v6.14 into tip.

The following changes since commit 63a48181fbcddefe5fb4c6618938bb64c543945b:

  smp/scf: Evaluate local cond_func() before IPI side-effects (2024-12-05 14:25:28 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/boqun/linux.git tags/lockdep-for-tip.20241220

for you to fetch changes up to fbd7a5a0359bc770e898d918d84977ea61163aad:

  rust: sync: Add lock::Backend::assert_is_held() (2024-12-19 14:04:42 -0800)


I combined lockdep and Rust locking changes into one pull-request,
because it's easy in that way for me, but should you want two different
pull requests, please let me know.

I keep all the Acked-bys in the MAINTAINERS changes, but feel free to
drop them because it's going via tip. Again, thanks for the trust and
thank Miguel for the support!

Regards,
Boqun

----------------------------------------------------------------
Lockdep changes for v6.14:

- Use swap() macro in the ww_mutex test.
- Minor fixes and documentation for lockdep configs on internal data structure sizes.
- Some "-Wunused-function" warning fixes for Clang.

Rust locking changes for v6.14:

- Add Rust locking files into LOCKING PRIMITIVES maintainer entry.
- Add `Lock<(), ..>::from_raw()` function to support abstraction on low level locking.
- Expose `Guard::new()` for public usage and add type alias for spinlock and mutex guards.
- Add lockdep checking when creating a new lock `Guard`.

----------------------------------------------------------------
Andy Shevchenko (2):
      lockdep: Mark chain_hlock_class_idx() with __maybe_unused
      lockdep: Move lockdep_assert_locked() under #ifdef CONFIG_PROVE_LOCKING

Boqun Feng (1):
      locking: MAINTAINERS: Start watching Rust locking primitives

Carlos Llamas (3):
      lockdep: Fix upper limit for LOCKDEP_*_BITS configs
      lockdep: Clarify size for LOCKDEP_*_BITS configs
      lockdep: Document MAX_LOCKDEP_CHAIN_HLOCKS calculation

Lyude Paul (5):
      rust: sync: Add Lock::from_raw() for Lock<(), B>
      rust: sync: Make Guard::new() public
      rust: sync: Add MutexGuard type alias
      rust: sync: Add SpinLockGuard type alias
      rust: sync: Add lock::Backend::assert_is_held()

Thorsten Blum (1):
      locking/ww_mutex/test: Use swap() macro

 MAINTAINERS                        |  7 ++++++-
 kernel/locking/lockdep.c           |  4 +++-
 kernel/locking/lockdep_internals.h |  3 ++-
 kernel/locking/test-ww_mutex.c     |  9 +++------
 lib/Kconfig.debug                  | 18 +++++++++---------
 rust/helpers/mutex.c               |  5 +++++
 rust/helpers/spinlock.c            |  5 +++++
 rust/kernel/sync.rs                |  4 ++--
 rust/kernel/sync/lock.rs           | 35 ++++++++++++++++++++++++++++++++++-
 rust/kernel/sync/lock/mutex.rs     | 13 +++++++++++++
 rust/kernel/sync/lock/spinlock.rs  | 13 +++++++++++++
 11 files changed, 95 insertions(+), 21 deletions(-)

             reply	other threads:[~2024-12-21  0:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-21  0:00 Boqun Feng [this message]
2024-12-22 11:44 ` [GIT PULL] LOCKDEP and Rust locking changes for v6.14 Peter Zijlstra

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=Z2YFO5zr9vm5kdjb@tardis.local \
    --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=gary@garyguo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=lyude@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