From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "Danilo Krummrich" <dakr@kernel.org>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rust/revocable: add try_with() convenience method
Date: Fri, 14 Mar 2025 00:11:31 +0900 [thread overview]
Message-ID: <D8F8GNNJ52JQ.1ZXW618MPFIYD@nvidia.com> (raw)
In-Reply-To: <Z9Lto6tbWS0kR6gK@pollux>
On Thu Mar 13, 2025 at 11:37 PM JST, Danilo Krummrich wrote:
> Hi Alex,
>
> Thanks for looking into this!
>
> On Thu, Mar 13, 2025 at 09:40:59PM +0900, Alexandre Courbot wrote:
>> Revocable::try_access() returns a guard through which the wrapped object
>> can be accessed. Code that can sleep is not allowed while the guard is
>> held ; thus, it is common that the caller will explicitly need to drop
>> it before running sleepable code, e.g:
>>
>> let b = bar.try_access()?;
>> let reg = b.readl(...);
>>
>> // Don't forget this or things could go wrong!
>> drop(b);
>>
>> something_that_might_sleep();
>>
>> let b = bar.try_access()?;
>> let reg2 = b.readl(...);
>
> Ideally, we get klint to protect us against those kind of mistakes too.
Yes, but even with klint I find it easier to delimitate the critical
sections explicitly and not having to remember about dropping the guard
when needed.
>
>> This is arguably error-prone. try_with() and try_with_ok() provides an
>> arguably safer alternative, by taking a closure that is run while the
>> guard is held, and by dropping the guard automatically after the closure
>> completes. This way, code can be organized more clearly around the
>> critical sections and the risk is forgetting to release the guard when
>> needed is considerably reduced:
>>
>> let reg = bar.try_with_ok(|b| b.readl(...))?;
>>
>> something_that_might_sleep();
>>
>> let reg2 = bar.try_with_ok(|b| b.readl(...))?;
>
> However, that's much more convenient and a great improvement.
>
> Feel free to add
>
> Acked-by: Danilo Krummrich <dakr@kernel.org>
Thanks!
>
>>
>> Unlike try_access() which returns an Option, try_with() and
>> try_with_ok() return Err(ENXIO) if the object cannot be acquired. The
>> Option returned by try_access() is typically converted to an error in
>> practice, so this saves one step for the caller.
>>
>> try_with() requires the callback itself to return a Result that is
>> passed to the caller. try_with_ok() accepts a callback that never fails.
>>
>> Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
>
> Since I proposed something like that in one of the nova threads (and in Zulip),
> feel free to also add
>
> Suggested-by: Danilo Krummrich <dakr@kernel.org>
Will do. I wasn't aware of this discussion, please let me know if I have
omitted something from your suggestion (like better method names, for
instance :)).
prev parent reply other threads:[~2025-03-13 15:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 12:40 [PATCH] rust/revocable: add try_with() convenience method Alexandre Courbot
2025-03-13 14:19 ` Benno Lossin
2025-03-13 15:08 ` Alexandre Courbot
2025-03-13 15:38 ` Benno Lossin
2025-03-13 15:48 ` Danilo Krummrich
2025-03-13 17:50 ` Benno Lossin
2025-03-15 14:07 ` Alexandre Courbot
2025-03-15 14:17 ` Danilo Krummrich
2025-03-15 14:26 ` Alexandre Courbot
2025-03-15 17:48 ` Benno Lossin
2025-03-16 12:20 ` Alexandre Courbot
2025-03-16 12:42 ` Danilo Krummrich
2025-03-13 14:37 ` Danilo Krummrich
2025-03-13 15:11 ` Alexandre Courbot [this message]
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=D8F8GNNJ52JQ.1ZXW618MPFIYD@nvidia.com \
--to=acourbot@nvidia.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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