From: "Onur Özkan" <work@onurozkan.dev>
To: Gary Guo <gary@garyguo.net>
Cc: rust-for-linux@vger.kernel.org, lossin@kernel.org,
lyude@redhat.com, ojeda@kernel.org, alex.gaynor@gmail.com,
boqun.feng@gmail.com, 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,
daniel.almeida@collabora.com, thomas.hellstrom@linux.intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v12 5/6] rust: ww_mutex: implement LockSet
Date: Thu, 15 Oct 2026 14:26:06 +0300 [thread overview]
Message-ID: <20261015112611.60966-1-work@onurozkan.dev> (raw)
In-Reply-To: <DM2UEMVP195X.WA9QG4BY453P@garyguo.net>
On Mon, 12 Oct 2026 13:02:15 +0100
Gary Guo <gary@garyguo.net> wrote:
> On Mon Oct 12, 2026 at 11:26 AM BST, Onur Özkan wrote:
> > LockSet is a high-level and safe API built on top of
> > ww_mutex which provides a safe and easy to use API
> > while keeping the ww_mutex semantics.
> >
> > When EDEADLK is hit it drops all held locks and waits for the
> > contended mutex. It then retries the given (by the user)
> > locking algorithm with that mutex held and the same acquire
> > context until it succeeds.
>
> Do we really need this, or this can be achieved by simple retry loops?
>
> fn retry_if_deadlock<R>(f: impl FnOnce() -> Result<R>) -> Result<R> {
> loop {
> match f() {
> Err(EDEADLK) => (),
> e => return e,
> }
> }
> }
>
> stack_pin_init!(let acq_ctx = AcquireCtx::new(&class));
> retry_if_deadlock(|| {
> let mut gaurd1 = acq_ctx.lock(&mutex1)?;
> let mut guard2 = acq_ctx.lock(&mutex2)?;
>
> acq_ctx.done();
>
> *guard1 += 1;
> *guard2 += 1;
> });
>
> I think the only difference is that the `LockSet` acquires the contending mutex
> first. However, I imagine we can solve this by having a wrapped `AcquireCtx`
> that provides that.
That's what LockSet already is. How would you design that wrapped AcquireCtx and
what would we gain by replacing LockSet with another wrapper?
You need to remember the contended mutex, release all acquired locks before
waiting for it and retry with that mutex held and the same acquire context. Also
for a dynamic set, you also need to keep the acquired locks held across loop
iterations and helper calls and handle repeated objects. With ordinary guards,
that bookkeeping falls on the caller unless the wrapper handles it. LockSet
already does all this.
Thanks,
Onur
>
> Best,
> Gary
>
> >
> > Signed-off-by: Onur Özkan <work@onurozkan.dev>
> > ---
> > rust/kernel/sync/lock/ww_mutex.rs | 6 +
> > rust/kernel/sync/lock/ww_mutex/lock_set.rs | 449 +++++++++++++++++++++
> > 2 files changed, 455 insertions(+)
> > create mode 100644 rust/kernel/sync/lock/ww_mutex/lock_set.rs
>
next prev parent reply other threads:[~2026-10-15 11:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 10:26 [PATCH v12 0/6] rust: add ww_mutex support Onur Özkan
2026-10-12 10:26 ` [PATCH v12 1/6] rust: add C wrappers for ww_mutex inline functions Onur Özkan
2026-10-12 11:41 ` Gary Guo
2026-10-12 10:26 ` [PATCH v12 2/6] ww_mutex: add ww_class field unconditionally Onur Özkan
2026-10-12 11:42 ` Gary Guo
2026-10-15 11:37 ` Onur Özkan
2026-10-12 10:26 ` [PATCH v12 3/6] rust: implement Class for ww_class support Onur Özkan
2026-10-12 11:03 ` Gary Guo
2026-10-12 11:26 ` Onur Özkan
2026-10-12 10:26 ` [PATCH v12 4/6] rust: ww_mutex: add Mutex, AcquireCtx and MutexGuard Onur Özkan
2026-10-12 11:40 ` Gary Guo
2026-10-15 12:13 ` Onur Özkan
2026-10-15 14:10 ` Gary Guo
2026-10-12 10:26 ` [PATCH v12 5/6] rust: ww_mutex: implement LockSet Onur Özkan
2026-10-12 12:02 ` Gary Guo
2026-10-15 11:26 ` Onur Özkan [this message]
2026-10-15 11:53 ` Gary Guo
2026-10-15 12:26 ` Onur Özkan
2026-10-15 14:00 ` Gary Guo
2026-10-12 10:26 ` [PATCH v12 6/6] MAINTAINERS: add Onur Özkan as WW MUTEX maintainer 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=20261015112611.60966-1-work@onurozkan.dev \
--to=work@onurozkan.dev \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.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=thomas.hellstrom@linux.intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.