From: "Onur Özkan" <work@onurozkan.dev>
To: "Onur Özkan" <work@onurozkan.dev>
Cc: rcu@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org, ojeda@kernel.org, boqun@kernel.org,
gary@garyguo.net, bjorn3_gh@protonmail.com, lossin@kernel.org,
a.hindborg@kernel.org, aliceryhl@google.com, tmgross@umich.edu,
dakr@kernel.org, peterz@infradead.org, fujita.tomonori@gmail.com,
tamird@kernel.org, jiangshanlai@gmail.com, paulmck@kernel.org,
josh@joshtriplett.org, rostedt@goodmis.org,
mathieu.desnoyers@efficios.com
Subject: Re: [PATCH v7 3/4] rust: sync: add SRCU abstraction
Date: Thu, 28 May 2026 11:20:10 +0300 [thread overview]
Message-ID: <20260528082025.44414-1-work@onurozkan.dev> (raw)
In-Reply-To: <20260528062810.256212-4-work@onurozkan.dev>
On Thu, 28 May 2026 09:27:35 +0300
Onur Özkan <work@onurozkan.dev> wrote:
> Add a Rust abstraction for sleepable RCU (SRCU), backed by C srcu_struct.
> Provide FFI helpers and a safe wrapper with a guard-based API for read-side
> critical sections.
>
> Cleanup is handled via `PinnedDrop`, which explicitly drains pending grace
> periods and callbacks via `synchronize_srcu` and `srcu_barrier` before
> executing `cleanup_srcu_struct` to guarantee memory safety e.g. when there
> are leaked guards (via `mem::forget($guard)`).
>
> Signed-off-by: Onur Özkan <work@onurozkan.dev>
> ---
> rust/kernel/sync.rs | 2 +
> rust/kernel/sync/srcu.rs | 166 +++++++++++++++++++++++++++++++++++++++
> 2 files changed, 168 insertions(+)
> create mode 100644 rust/kernel/sync/srcu.rs
>
> diff --git a/rust/kernel/sync.rs b/rust/kernel/sync.rs
> index 993dbf2caa0e..0d6a5f1300c3 100644
> --- a/rust/kernel/sync.rs
> +++ b/rust/kernel/sync.rs
> @@ -21,6 +21,7 @@
> pub mod rcu;
> mod refcount;
> mod set_once;
> +pub mod srcu;
>
> pub use arc::{Arc, ArcBorrow, UniqueArc};
> pub use completion::Completion;
> @@ -31,6 +32,7 @@
> pub use locked_by::LockedBy;
> pub use refcount::Refcount;
> pub use set_once::SetOnce;
> +pub use srcu::Srcu;
>
> /// Represents a lockdep class.
> ///
> diff --git a/rust/kernel/sync/srcu.rs b/rust/kernel/sync/srcu.rs
> new file mode 100644
> index 000000000000..343f00d070c7
> --- /dev/null
> +++ b/rust/kernel/sync/srcu.rs
> @@ -0,0 +1,166 @@
> +// SPDX-License-Identifier: GPL-2.0
> +
> +//! Sleepable read-copy update (SRCU) support.
> +//!
> +//! C header: [`include/linux/srcu.h`](srctree/include/linux/srcu.h)
> +
> +use crate::{
> + bindings,
> + error::to_result,
> + prelude::*,
> + sync::LockClassKey,
> + types::{
> + NotThreadSafe,
> + Opaque, //
> + },
> +};
> +
> +use pin_init::pin_data;
> +
> +/// Creates an [`Srcu`] initialiser with the given name and a newly-created lock class.
> +#[doc(hidden)]
> +#[macro_export]
> +macro_rules! new_srcu {
> + ($($name:literal)?) => {
> + $crate::sync::Srcu::new($crate::optional_name!($($name)?), $crate::static_lock_class!())
> + };
> +}
> +pub use new_srcu;
> +
> +/// Sleepable read-copy update primitive.
> +///
> +/// SRCU readers may sleep while holding the read-side guard.
> +///
> +/// The destructor waits for active readers and callbacks, so it may sleep.
> +/// If a read-side guard has been leaked, dropping an [`Srcu`] may never return.
> +///
> +/// # Invariants
> +///
> +/// This represents a valid `struct srcu_struct` initialized by the C SRCU API
> +/// and it remains pinned and valid until the pinned destructor runs.
> +#[repr(transparent)]
> +#[pin_data(PinnedDrop)]
> +pub struct Srcu {
> + #[pin]
> + inner: Opaque<bindings::srcu_struct>,
> +}
> +
> +impl Srcu {
> + /// Creates a new SRCU instance.
> + #[inline]
> + pub fn new(name: &'static CStr, key: Pin<&'static LockClassKey>) -> impl PinInit<Self, Error> {
> + try_pin_init!(Self {
> + // INVARIANT: On success, the C initializer creates a valid `srcu_struct` and
> + // it remains pinned until `PinnedDrop` runs.
> + inner <- Opaque::try_ffi_init(|ptr: *mut bindings::srcu_struct| {
> + // SAFETY: `ptr` points to valid uninitialised memory for a `srcu_struct`.
> + to_result(unsafe {
> + bindings::init_srcu_struct_with_key(ptr, name.as_char_ptr(), key.as_ptr())
> + })
> + }),
> + })
> + }
> +
> + /// Enters an SRCU read-side critical section.
> + ///
> + /// Leaking the returned [`Guard`] leaves the SRCU read-side critical
> + /// section active and makes `drop` sleep forever.
> + #[inline]
> + pub fn read_lock(&self) -> Guard<'_> {
> + // SAFETY: By the type invariants, `self` contains a valid `struct srcu_struct`.
> + let idx = unsafe { bindings::srcu_read_lock(self.inner.get()) };
> +
> + // INVARIANT: `idx` was returned by `srcu_read_lock()` for this `Srcu`.
> + Guard {
> + srcu: self,
> + idx,
> + _not_send: NotThreadSafe,
> + }
> + }
> +
> + /// Waits until all pre-existing SRCU readers have completed.
> + #[inline]
> + pub fn synchronize(&self) {
> + // SAFETY: By the type invariants, `self` contains a valid `struct srcu_struct`.
> + unsafe { bindings::synchronize_srcu(self.inner.get()) };
> + }
> +
> + /// Waits until all pre-existing SRCU readers have completed, expedited.
> + ///
> + /// This requests a lower-latency grace period than [`Srcu::synchronize`] typically
> + /// at the cost of higher system-wide overhead. Prefer [`Srcu::synchronize`] by default
> + /// and use this variant only when reducing reset or teardown latency is more important
> + /// than the extra cost.
> + #[inline]
> + pub fn synchronize_expedited(&self) {
> + // SAFETY: By the type invariants, `self` contains a valid `struct srcu_struct`.
> + unsafe { bindings::synchronize_srcu_expedited(self.inner.get()) };
> + }
> +}
> +
> +#[pinned_drop]
> +impl PinnedDrop for Srcu {
> + fn drop(self: Pin<&mut Self>) {
> + let ptr = self.inner.get();
> +
> + // SAFETY: By the type invariants, `self` contains a valid and pinned `struct srcu_struct`
> + // and `srcu_readers_active()` only checks the active reader count.
> + if unsafe { bindings::srcu_readers_active(ptr) } {
> + crate::pr_warn!(
> + "Leaked `Guard` detected while dropping SRCU; drop will block forever.\n"
> + );
> + }
> +
> + // `cleanup_srcu_struct()` may return early if readers are still active. Because `Srcu`
> + // owns the embedded `srcu_struct`, returning from `drop` in that state could free memory
> + // that is still referenced by the C side.
> + //
> + // Wait for all readers to complete first. If any `Guard` was leaked, `synchronize_srcu()`
> + // will sleep forever.
> + //
> + // SAFETY: By the type invariants, `self` contains a valid and pinned `struct srcu_struct`.
> + unsafe { bindings::synchronize_srcu(ptr) };
Sashiko got a good point here which is calling synchronize_srcu() only if there
are active readers. That's a nice low-effort improvement we can have in the next
version.
Onur
> +
> + // Ensure all SRCU callbacks have been finished before freeing.
> + // SAFETY: By the type invariants, `self` contains a valid and pinned `struct srcu_struct`.
> + unsafe { bindings::srcu_barrier(ptr) };
> +
> + // SAFETY: By the type invariants, `self` contains a valid and pinned `struct srcu_struct`.
> + unsafe { bindings::cleanup_srcu_struct(ptr) };
> + }
> +}
> +
> +// SAFETY: `srcu_struct` may be shared and used across threads.
> +unsafe impl Send for Srcu {}
> +// SAFETY: `srcu_struct` may be shared and used concurrently.
> +unsafe impl Sync for Srcu {}
> +
> +/// Guard for an active SRCU read-side critical section on a particular [`Srcu`].
> +///
> +/// Leaking this guard with [`core::mem::forget`] leaves the SRCU read-side
> +/// critical section active and makes dropping the associated [`Srcu`] sleep forever.
> +///
> +/// # Invariants
> +///
> +/// `idx` is the index returned by `srcu_read_lock()` for `srcu`.
> +#[must_use = "if unused, the lock will be immediately unlocked"]
> +pub struct Guard<'a> {
> + srcu: &'a Srcu,
> + idx: i32,
> + _not_send: NotThreadSafe,
> +}
> +
> +impl Guard<'_> {
> + /// Explicitly releases the SRCU read-side critical section.
> + #[inline]
> + pub fn unlock(self) {}
> +}
> +
> +impl Drop for Guard<'_> {
> + #[inline]
> + fn drop(&mut self) {
> + // SAFETY: `Guard` is only constructible through `Srcu::read_lock()`,
> + // which returns a valid index for the SRCU instance.
> + unsafe { bindings::srcu_read_unlock(self.srcu.inner.get(), self.idx) };
> + }
> +}
> --
> 2.51.2
>
next prev parent reply other threads:[~2026-05-28 8:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 6:27 [PATCH v7 0/4] rust: helpers: add SRCU helpers Onur Özkan
2026-05-28 6:27 ` [PATCH v7 1/4] " Onur Özkan
2026-05-28 6:27 ` [PATCH v7 2/4] srcu: expose srcu_readers_active() Onur Özkan
2026-05-28 6:27 ` [PATCH v7 3/4] rust: sync: add SRCU abstraction Onur Özkan
2026-05-28 8:20 ` Onur Özkan [this message]
2026-05-28 8:35 ` Onur Özkan
2026-05-28 12:23 ` Gary Guo
2026-05-29 6:57 ` Onur Özkan
2026-05-29 12:07 ` Gary Guo
2026-05-29 12:29 ` Onur Özkan
2026-05-29 12:41 ` Gary Guo
2026-05-29 12:49 ` Onur Özkan
2026-05-31 18:04 ` Paul E. McKenney
2026-05-29 15:36 ` Paul E. McKenney
2026-05-30 6:27 ` Onur Özkan
2026-05-31 18:06 ` Paul E. McKenney
2026-05-31 18:53 ` Miguel Ojeda
2026-05-31 19:11 ` Onur Özkan
2026-06-01 9:29 ` Miguel Ojeda
2026-06-04 17:50 ` Paul E. McKenney
2026-05-28 6:27 ` [PATCH v7 4/4] MAINTAINERS: add Rust SRCU files to SRCU entry Onur Özkan
2026-05-28 18:50 ` [PATCH v7 0/4] rust: helpers: add SRCU helpers Paul E. McKenney
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=20260528082025.44414-1-work@onurozkan.dev \
--to=work@onurozkan.dev \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=ojeda@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@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