linux-kernel - Re: [PATCH locking 00/11] LOCKDEP and Rust locking changes for v6.15

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Z8uI6aOd79xe32CS@gmail.com>
Date: Sat, 8 Mar 2025 01:01:45 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Boqun Feng <boqun.feng@...il.com>
Cc: Peter Zijlstra <peterz@...radead.org>, Will Deacon <will@...nel.org>,
	Waiman Long <longman@...hat.com>, linux-kernel@...r.kernel.org,
	Miguel Ojeda <ojeda@...nel.org>,
	Alex Gaynor <alex.gaynor@...il.com>, Gary Guo <gary@...yguo.net>,
	Björn Roy Baron <bjorn3_gh@...tonmail.com>,
	Benno Lossin <benno.lossin@...ton.me>,
	Andreas Hindborg <a.hindborg@...nel.org>,
	Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
	"open list:RUST:Keyword:b(?i:rust)b" <rust-for-linux@...r.kernel.org>
Subject: Re: [PATCH locking 00/11] LOCKDEP and Rust locking changes for v6.15


* Boqun Feng <boqun.feng@...il.com> wrote:

> Hi Ingo & Peter,
> 
> As discussed, I'm resending the pull request for lockdep and Rust
> locking for v6.15 in the format of email patches. I dropped one patch
> and will postpone it for v6.16 because of a bug [1], and I think the fix
> [2] needs more reviews.
> 
> [1]: https://lore.kernel.org/lkml/20250306122413.GBZ8mT7Z61Tmgnh5Y9@fat_crate.local/
> [2]: https://lore.kernel.org/lkml/Z8t8imzJVhWyDvhC@boqun-archlinux/
> 
> Regards,
> Boqun
> 
> 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
> 
> 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()

Thanks Boqun!

I've applied these 3 patches to the tip:locking/urgent tree:

  locking/semaphore: Use wake_q to wake up processes outside lock critical section
  locking/rtmutex: Use the 'struct' keyword in kernel-doc comment
  rust: lockdep: Remove support for dynamically allocated LockClassKeys

As a general rule, if a patch is marked Cc: stable, it must also be 
applied to current upstream.

I have applied the others to tip:locking/core:

  locking/lock_events: Add locking events for rtmutex slow pathsa94d32446ab5 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()
  rust: sync: Add accessor for the lock behind a given guard
  rust: sync: lock: Add an example for Guard:: Lock_ref()
  rust: sync: condvar: Add wait_interruptible_freezable()
  rust: lockdep: Use Pin for all LockClassKey usages

I cleaned up changelogs where necessary - for example we generally 
don't include printk timestamps in changelogs, unless it's relevant, 
plus there were a number of typos and grammar mistakes left in some of 
the changelogs.

Thanks,

	Ingo