From: Alice Ryhl <aliceryhl@google.com>
To: "Boqun Feng" <boqun@kernel.org>, "Gary Guo" <gary@garyguo.net>,
"Lyude Paul" <lyude@redhat.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Onur Özkan" <work@onurozkan.dev>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Carlos Llamas" <cmllamas@google.com>
Cc: "Luis Chamberlain" <mcgrof@kernel.org>,
"Petr Pavlu" <petr.pavlu@suse.com>,
"Daniel Gomez" <da.gomez@kernel.org>,
"Sami Tolvanen" <samitolvanen@google.com>,
"Aaron Tomlin" <atomlin@atomlin.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Tamir Duberstein" <tamird@kernel.org>,
"Alexandre Courbot" <acourbot@nvidia.com>,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org,
"Alice Ryhl" <aliceryhl@google.com>
Subject: [PATCH 2/3] rust: sync: add SetOnce::try_get_or_populate()
Date: Wed, 22 Jul 2026 09:16:03 +0000 [thread overview]
Message-ID: <20260722-setonce-populate-v1-2-fa7455c26c42@google.com> (raw)
In-Reply-To: <20260722-setonce-populate-v1-0-fa7455c26c42@google.com>
The SetOnce::populate() method does not internally synchronize callers
that fail to populate the value with the successful call. This means
that naive loops using as_ref() and populate() can lead to spinning on
the initialization, which is best avoided. Thus, provide a helper that
avoids this issue using a user-provided lock.
One potential alternative is to change populate() so that the failing
caller actually does synchronize with the successful call to populate().
However, this is somewhat tricky:
* There are users of SetOnce that construct it in const context, and we
currently don't have the ability to do that for most locks, so we
cannot easily add a lock to SetOnce.
* Just spinning on the atomic is undesirable unless we disable
preemption in the success path. If we do disable preemption, then that
raises complications for handling the PREEMPT_RT case.
* It also raises questions about deadlocks if populate() is called from
irqs.
By using a user-provided lock, we do not have to worry about these
issues inside SetOnce.
Signed-off-by: Alice Ryhl <aliceryhl@google.com>
---
rust/kernel/sync/set_once.rs | 43 +++++++++++++++++++++++++++++++++++++++----
1 file changed, 39 insertions(+), 4 deletions(-)
diff --git a/rust/kernel/sync/set_once.rs b/rust/kernel/sync/set_once.rs
index a78f8c8e87db..d9cc598a8d78 100644
--- a/rust/kernel/sync/set_once.rs
+++ b/rust/kernel/sync/set_once.rs
@@ -2,11 +2,18 @@
//! A container that can be initialized at most once.
-use super::atomic::{
- ordering::{Acquire, Relaxed, Release},
- Atomic,
-};
use core::{cell::UnsafeCell, mem::MaybeUninit};
+use kernel::sync::{
+ atomic::{
+ ordering::{
+ Acquire,
+ Relaxed,
+ Release, //
+ },
+ Atomic, //
+ },
+ lock, //
+};
/// A container that can be populated at most once. Thread safe.
///
@@ -104,6 +111,34 @@ pub fn populate(&self, value: T) -> Result<&T, T> {
}
}
+ /// Get the value, or populate it if it's missing.
+ ///
+ /// This method is useful to avoid spinning on the internal atomic state. If all writers call
+ /// this method with the same lock, then they are synchronized with each other and it's
+ /// guaranteed that no caller will attempt to invoke [`SetOnce::populate`] more than once.
+ pub fn try_get_or_populate<F, E, U, B>(&self, lock: &lock::Lock<U, B>, f: F) -> Result<&T, E>
+ where
+ B: lock::Backend,
+ F: FnOnce() -> Result<T, E>,
+ {
+ if let Some(value) = self.as_ref() {
+ return Ok(value);
+ }
+
+ let mut to_insert = f()?;
+ loop {
+ if let Some(value) = self.as_ref() {
+ return Ok(value);
+ }
+
+ let _guard = lock.lock();
+ match self.populate(to_insert) {
+ Ok(value) => return Ok(value),
+ Err(ret) => to_insert = ret,
+ }
+ }
+ }
+
/// Get a copy of the contained object.
///
/// Returns [`None`] if the [`SetOnce`] is empty.
--
2.55.0.229.g6434b31f56-goog
next prev parent reply other threads:[~2026-07-22 9:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 9:16 [PATCH 0/3] rust: sync: add SetOnce::try_get_or_populate() Alice Ryhl
2026-07-22 9:16 ` [PATCH 1/3] rust: sync: return `Result<&T, T>` from `SetOnce::populate()` Alice Ryhl
2026-07-29 14:09 ` Alexandre Courbot
2026-07-22 9:16 ` Alice Ryhl [this message]
2026-07-29 14:05 ` [PATCH 2/3] rust: sync: add SetOnce::try_get_or_populate() Alexandre Courbot
2026-07-29 14:23 ` Boqun Feng
2026-07-22 9:16 ` [PATCH 3/3] rust_binder: use SetOnce::try_get_or_populate() Alice Ryhl
2026-07-29 14:12 ` [PATCH 0/3] rust: sync: add SetOnce::try_get_or_populate() Alexandre Courbot
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=20260722-setonce-populate-v1-2-fa7455c26c42@google.com \
--to=aliceryhl@google.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=atomlin@atomlin.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=cmllamas@google.com \
--cc=da.gomez@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=lyude@redhat.com \
--cc=mcgrof@kernel.org \
--cc=ojeda@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=samitolvanen@google.com \
--cc=tamird@kernel.org \
--cc=tmgross@umich.edu \
--cc=work@onurozkan.dev \
/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