[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241120223442.2491136-1-lyude@redhat.com>
Date: Wed, 20 Nov 2024 17:30:40 -0500
From: Lyude Paul <lyude@...hat.com>
To: rust-for-linux@...r.kernel.org
Cc: linux-kernel@...r.kernel.org,
Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Boqun Feng <boqun.feng@...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>
Subject: [PATCH 0/3] rust: sync: Add Lock::is_locked()
Now that we expose Guard::new() outside of the lock module, I figured it
would be a good idea for us to actually add some debug assertions to
ensure that callers outside of this module don't call Guard::new() for
locks they don't actually hold.
This series adds the ability to do so, while also making sure that we
don't needlessly run these debug assertions for the more common usecase
of acquiring a lock in safe rust code.
Lyude Paul (3):
rust: sync: Add Lock::is_locked()
rust: sync: Assert Lock::is_locked in Guard::new for debug builds
rust: sync: Add Guard::new_unchecked()
rust/helpers/spinlock.c | 5 ++++
rust/kernel/sync/lock.rs | 42 +++++++++++++++++++++++++++++--
rust/kernel/sync/lock/mutex.rs | 5 ++++
rust/kernel/sync/lock/spinlock.rs | 5 ++++
4 files changed, 55 insertions(+), 2 deletions(-)
base-commit: b2603f8ac8217bc59f5c7f248ac248423b9b99cb
prerequisite-patch-id: 8c65a39abe47832d0c98c9c266b4b9348fb3526a
prerequisite-patch-id: 211faf8533feec77907b0a1b9b2f788e72c5ac58
--
2.47.0
Powered by blists - more mailing lists