From: "Onur Özkan" <work@onurozkan.dev>
To: Daniel Almeida <daniel.almeida@collabora.com>
Cc: rust-for-linux@vger.kernel.org, lossin@kernel.org,
lyude@redhat.com, ojeda@kernel.org, alex.gaynor@gmail.com,
boqun.feng@gmail.com, gary@garyguo.net, a.hindborg@kernel.org,
aliceryhl@google.com, tmgross@umich.edu, dakr@kernel.org,
peterz@infradead.org, mingo@redhat.com, will@kernel.org,
longman@redhat.com, felipe_life@live.com, daniel@sedlak.dev,
bjorn3_gh@protonmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 4/6] rust: ww_mutex: add Mutex, AcquireCtx and MutexGuard
Date: Tue, 25 Nov 2025 21:59:19 +0300 [thread overview]
Message-ID: <20251125215919.6af03a2e@nimda.home> (raw)
In-Reply-To: <A3A21F48-4F9A-46CD-9CC8-80A55B32CDE2@collabora.com>
On Tue, 25 Nov 2025 15:32:08 -0300
Daniel Almeida <daniel.almeida@collabora.com> wrote:
[...]
> > + /// Similar to `lock`, but can be interrupted by signals.
> > + ///
> > + /// # Safety
> > + ///
> > + /// The given `mutex` must be created with the [`Class`] that
> > was used
> > + /// to initialize this [`AcquireCtx`].
> > + pub unsafe fn lock_interruptible<'a, T>(
> > + &'a self,
> > + mutex: &'a Mutex<'a, T>,
> > + ) -> Result<MutexGuard<'a, T>> {
> > + // SAFETY: By the safety contract, `mutex` belongs to the
> > same `Class`
> > + // as `self` does.
> > + unsafe { lock_common(mutex, Some(self),
> > LockKind::Interruptible) }
> > + }
> > +
> > + /// Locks the given mutex on this [`AcquireCtx`] using the
> > slow path.
> > + ///
> > + /// This function should be used when `lock` fails (typically
> > due to a potential deadlock).
> > + ///
> > + /// # Safety
> > + ///
> > + /// The given `mutex` must be created with the [`Class`] that
> > was used
> > + /// to initialize this [`AcquireCtx`].
>
> I’m assuming we either can’t or otherwise don’t want to store this in
> the Mutex itself?
>
> IOW: the class is ’static IIUC, so it’s always safe to store a
> reference anyways, at the cost of providing the storage.
>
We used to do this but I had to revert them when I implemented
`from_raw` functions. I wrote about it on [1], let me know what you
think about the solution idea I wrote there.
[1]: https://lore.kernel.org/all/20251124184928.30b8bbaf@nimda/
> > + pub unsafe fn lock_slow<'a, T>(&'a self, mutex: &'a Mutex<'a,
> > T>) -> Result<MutexGuard<'a, T>> {
> > + // SAFETY: By the safety contract, `mutex` belongs to the
> > same `Class`
> > + // as `self` does.
> > + unsafe { lock_common(mutex, Some(self), LockKind::Slow) }
> > + }
> > +
> > + /// Similar to `lock_slow`, but can be interrupted by signals.
> > + ///
> > + /// # Safety
> > + ///
> > + /// The given `mutex` must be created with the [`Class`] that
> > was used
> > + /// to initialize this [`AcquireCtx`].
> > + pub unsafe fn lock_slow_interruptible<'a, T>(
> > + &'a self,
> > + mutex: &'a Mutex<'a, T>,
> > + ) -> Result<MutexGuard<'a, T>> {
> > + // SAFETY: By the safety contract, `mutex` belongs to the
> > same `Class`
> > + // as `self` does.
> > + unsafe { lock_common(mutex, Some(self),
> > LockKind::SlowInterruptible) }
> > + }
> > +
> > + /// Tries to lock the mutex on this [`AcquireCtx`] without
> > blocking.
> > + ///
> > + /// Unlike `lock`, no deadlock handling is performed.
>
> You can use [`lock`] here for better docs.
>
I will update it as [`Self::lock`] ([`lock`] will not work). There are
some other lines where I need to do the same thing.
> > + ///
> > + /// # Safety
> > + ///
> > + /// The given `mutex` must be created with the [`Class`] that
[...]
BR,
Onur
next prev parent reply other threads:[~2025-11-25 18:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-01 16:10 [PATCH v7 0/6] rust: add `ww_mutex` support Onur Özkan
2025-11-01 16:10 ` [PATCH v7 1/6] rust: add C wrappers for ww_mutex inline functions Onur Özkan
2025-11-21 19:08 ` Lyude Paul
2025-11-25 15:53 ` Daniel Almeida
2025-11-01 16:10 ` [PATCH v7 2/6] rust: implement `Class` for ww_class support Onur Özkan
2025-11-21 19:15 ` Lyude Paul
2025-11-27 8:57 ` Onur Özkan
2025-11-25 16:12 ` Daniel Almeida
2025-11-01 16:10 ` [PATCH v7 3/6] rust: error: add EDEADLK Onur Özkan
2025-11-21 19:49 ` Lyude Paul
2025-11-25 16:13 ` Daniel Almeida
2025-11-01 16:10 ` [PATCH v7 4/6] rust: ww_mutex: add Mutex, AcquireCtx and MutexGuard Onur Özkan
2025-11-21 21:00 ` Lyude Paul
2025-11-27 9:24 ` Onur Özkan
2025-11-28 11:37 ` Onur Özkan
2025-11-25 18:32 ` Daniel Almeida
2025-11-25 18:59 ` Onur Özkan [this message]
2025-11-01 16:10 ` [PATCH v7 5/6] rust: ww_mutex: implement LockSet Onur Özkan
2025-11-21 22:34 ` Lyude Paul
2025-11-24 15:49 ` Onur Özkan
2025-11-25 19:01 ` Daniel Almeida
2025-11-25 20:08 ` Onur Özkan
2025-11-25 21:35 ` Lyude Paul
2025-11-25 21:47 ` Daniel Almeida
2025-11-25 22:14 ` Lyude Paul
2025-11-27 10:16 ` Onur Özkan
2025-11-27 13:46 ` Daniel Almeida
2025-11-01 16:10 ` [PATCH v7 6/6] rust: add test coverage for ww_mutex implementation Onur Özkan
2025-11-10 5:28 ` [PATCH v7 0/6] rust: add `ww_mutex` support Onur Özkan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251125215919.6af03a2e@nimda.home \
--to=work@onurozkan.dev \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=daniel@sedlak.dev \
--cc=felipe_life@live.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=lossin@kernel.org \
--cc=lyude@redhat.com \
--cc=mingo@redhat.com \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).