[PATCH v2] rust: locks: Add `get_mut` method to `Lock`

From: Mathys-Gasnier via B4 Relay
Date: Mon Feb 12 2024 - 09:15:42 EST


From: Mathys-Gasnier <mathys35.gasnier@xxxxxxxxx>

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.

Reviewed-by: Martin Rodriguez Reboredo <yakoyoku@xxxxxxxxx>
Signed-off-by: Mathys-Gasnier <mathys35.gasnier@xxxxxxxxx>
---
Changes in v2:
- Improved doc comment.
- Link to v1: https://lore.kernel.org/r/20240209-rust-locks-get-mut-v1-1-ce351fc3de47@xxxxxxxxx
---
rust/kernel/sync/lock.rs | 7 +++++++
1 file changed, 7 insertions(+)

diff --git a/rust/kernel/sync/lock.rs b/rust/kernel/sync/lock.rs
index f12a684bc957..d15af6625d01 100644
--- a/rust/kernel/sync/lock.rs
+++ b/rust/kernel/sync/lock.rs
@@ -121,6 +121,13 @@ 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
+ /// Having a mutable reference to the lock guarantees that no other threads have access to the lock.
+ /// Making it safe to get a mutable reference to the lock content.
+ 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@xxxxxxxxx>