[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAH5fLghTKpLs=Wb03cjx0LRQbZgmXRoMNy1cyheb7cQRL0mjsw@mail.gmail.com>
Date: Mon, 12 Feb 2024 15:22:14 +0100
From: Alice Ryhl <aliceryhl@...gle.com>
To: mathys35.gasnier@...il.com
Cc: 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>,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
Martin Rodriguez Reboredo <yakoyoku@...il.com>
Subject: Re: [PATCH v2] rust: locks: Add `get_mut` method to `Lock`
On Mon, Feb 12, 2024 at 3:13 PM Mathys-Gasnier via B4 Relay
<devnull+mathys35.gasnier.gmail.com@...nel.org> wrote:
> + /// 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()
> + }
It's impossible to call this method. You can never have a mutable
reference to a Linux mutex because we pin our locks. At most, you can
have a Pin<&mut Self>.
Alice
Powered by blists - more mailing lists