[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240209-rust-locks-get-mut-v1-1-ce351fc3de47@gmail.com>
Date: Fri, 09 Feb 2024 17:22:24 +0100
From:
Mathys-Gasnier via B4 Relay <devnull+mathys35.gasnier.gmail.com@...nel.org>
To: Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>,
Wedson Almeida Filho <wedsonaf@...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@...sung.com>,
Alice Ryhl <aliceryhl@...gle.com>
Cc: rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
Mathys-Gasnier <mathys35.gasnier@...il.com>
Subject: [PATCH] rust: locks: Add `get_mut` method to `Lock`
From: Mathys-Gasnier <mathys35.gasnier@...il.com>
Having a mutable reference guarantees that no other threads have
access to the lock, so we can take advantage of that to grant callers
access to the protected data without the the cost of acquiring and
releasing the locks. Since the lifetime of the data is tied to the
mutable reference, the borrow checker guarantees that the usage is safe.
Signed-off-by: Mathys-Gasnier <mathys35.gasnier@...il.com>
---
rust/kernel/sync/lock.rs | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/rust/kernel/sync/lock.rs b/rust/kernel/sync/lock.rs
index f12a684bc957..7711c6313e14 100644
--- a/rust/kernel/sync/lock.rs
+++ b/rust/kernel/sync/lock.rs
@@ -121,6 +121,11 @@ pub fn lock(&self) -> Guard<'_, T, B> {
// SAFETY: The lock was just acquired.
unsafe { Guard::new(self, state) }
}
+
+ /// Gets the data contained in the lock
+ pub fn get_mut(&mut self) -> &mut T {
+ self.data.get_mut()
+ }
}
/// A lock guard.
---
base-commit: 711cbfc717650532624ca9f56fbaf191bed56e67
change-id: 20240118-rust-locks-get-mut-c42072101d7a
Best regards,
--
Mathys-Gasnier <mathys35.gasnier@...il.com>
Powered by blists - more mailing lists