All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@collabora.com>
To: Danilo Krummrich <dakr@kernel.org>
Cc: gregkh@linuxfoundation.org, rafael@kernel.org, ojeda@kernel.org,
	boqun.feng@gmail.com, gary@garyguo.net, bjorn3_gh@protonmail.com,
	lossin@kernel.org, a.hindborg@kernel.org, aliceryhl@google.com,
	tmgross@umich.edu, driver-core@lists.linux.dev,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
	Markus Probst <markus.probst@posteo.de>
Subject: Re: [PATCH] rust: devres: fix race condition due to nesting
Date: Fri, 6 Feb 2026 08:53:42 +0100	[thread overview]
Message-ID: <20260206085342.609ab3a1@fedora> (raw)
In-Reply-To: <20260205222529.91465-1-dakr@kernel.org>

On Thu,  5 Feb 2026 23:25:15 +0100
Danilo Krummrich <dakr@kernel.org> wrote:

> Commit f5d3ef25d238 ("rust: devres: get rid of Devres' inner Arc") did
> attempt to optimize away the internal reference count of Devres.
> 
> However, without an internal reference count, we can't support cases
> where Devres is indirectly nested, resulting into a deadlock.
> 
> Such indirect nesting easily happens in the following way:
> 
> A registration object (which is guarded by devres) hold a reference
> count of an object that holds a device resource guarded by devres
> itself.
> 
> For instance a drm::Registration holds a reference of a drm::Device. The
> drm::Device itself holds a device resource in its private data.
> 
> When the drm::Registration is dropped by devres, and it happens that it
> did hold the last reference count of the drm::Device, it also drops the
> device resource, which is guarded by devres itself.
> 
> Thus, resulting into a deadlock in the Devres destructor of the device
> resource, as in the following backtrace.
> 
> 	sysrq: Show Blocked State
> 	task:rmmod           state:D stack:0     pid:1331  tgid:1331  ppid:1330   task_flags:0x400100 flags:0x00000010
> 	Call trace:
> 	 __switch_to+0x190/0x294 (T)
> 	 __schedule+0x878/0xf10
> 	 schedule+0x4c/0xcc
> 	 schedule_timeout+0x44/0x118
> 	 wait_for_common+0xc0/0x18c
> 	 wait_for_completion+0x18/0x24
> 	 _RINvNtCs4gKlGRWyJ5S_4core3ptr13drop_in_placeINtNtNtCsgzhNYVB7wSz_6kernel4sync3arc3ArcINtNtBN_6devres6DevresmEEECsRdyc7Hyps3_15rust_driver_pci+0x68/0xe8 [rust_driver_pci]
> 	 _RINvNvNtCsgzhNYVB7wSz_6kernel6devres16register_foreign8callbackINtNtCs4gKlGRWyJ5S_4core3pin3PinINtNtNtB6_5alloc4kbox3BoxINtNtNtB6_4sync3arc3ArcINtB4_6DevresmEENtNtB1A_9allocator7KmallocEEECsRdyc7Hyps3_15rust_driver_pci+0x34/0xc8 [rust_driver_pci]
> 	 devm_action_release+0x14/0x20
> 	 devres_release_all+0xb8/0x118
> 	 device_release_driver_internal+0x1c4/0x28c
> 	 driver_detach+0x94/0xd4
> 	 bus_remove_driver+0xdc/0x11c
> 	 driver_unregister+0x34/0x58
> 	 pci_unregister_driver+0x20/0x80
> 	 __arm64_sys_delete_module+0x1d8/0x254
> 	 invoke_syscall+0x40/0xcc
> 	 el0_svc_common+0x8c/0xd8
> 	 do_el0_svc+0x1c/0x28
> 	 el0_svc+0x54/0x1d4
> 	 el0t_64_sync_handler+0x84/0x12c
> 	 el0t_64_sync+0x198/0x19c
> 
> In order to fix this, re-introduce the internal reference count.
> 
> Reported-by: Boris Brezillon <boris.brezillon@collabora.com>
> Closes: https://rust-for-linux.zulipchat.com/#narrow/channel/288089-General/topic/.E2.9C.94.20Deadlock.20caused.20by.20nested.20Devres/with/571242651
> Reported-by: Markus Probst <markus.probst@posteo.de>
> Closes: https://rust-for-linux.zulipchat.com/#narrow/channel/288089-General/topic/.E2.9C.94.20Devres.20inside.20Devres.20stuck.20on.20cleanup/with/571239721
> Reported-by: Alice Ryhl <aliceryhl@google.com>
> Closes: https://gitlab.freedesktop.org/panfrost/linux/-/merge_requests/56#note_3282757
> Fixes: f5d3ef25d238 ("rust: devres: get rid of Devres' inner Arc")
> Signed-off-by: Danilo Krummrich <dakr@kernel.org>

Tested-by: Boris Brezillon <boris.brezillon@collabora.com>

> ---
>  rust/kernel/devres.rs | 148 +++++++++++-------------------------------
>  1 file changed, 39 insertions(+), 109 deletions(-)
> 
> diff --git a/rust/kernel/devres.rs b/rust/kernel/devres.rs
> index cdc49677022a..ff66f561740a 100644
> --- a/rust/kernel/devres.rs
> +++ b/rust/kernel/devres.rs
> @@ -21,30 +21,11 @@
>      sync::{
>          aref::ARef,
>          rcu,
> -        Completion, //
> -    },
> -    types::{
> -        ForeignOwnable,
> -        Opaque,
> -        ScopeGuard, //
> +        Arc, //
>      },
> +    types::ForeignOwnable,
>  };
>  
> -use pin_init::Wrapper;
> -
> -/// [`Devres`] inner data accessed from [`Devres::callback`].
> -#[pin_data]
> -struct Inner<T: Send> {
> -    #[pin]
> -    data: Revocable<T>,
> -    /// Tracks whether [`Devres::callback`] has been completed.
> -    #[pin]
> -    devm: Completion,
> -    /// Tracks whether revoking [`Self::data`] has been completed.
> -    #[pin]
> -    revoke: Completion,
> -}
> -
>  /// This abstraction is meant to be used by subsystems to containerize [`Device`] bound resources to
>  /// manage their lifetime.
>  ///
> @@ -121,18 +102,13 @@ struct Inner<T: Send> {
>  /// # fn no_run(dev: &Device<Bound>) -> Result<(), Error> {
>  /// // SAFETY: Invalid usage for example purposes.
>  /// let iomem = unsafe { IoMem::<{ core::mem::size_of::<u32>() }>::new(0xBAAAAAAD)? };
> -/// let devres = KBox::pin_init(Devres::new(dev, iomem), GFP_KERNEL)?;
> +/// let devres = Devres::new(dev, iomem)?;
>  ///
>  /// let res = devres.try_access().ok_or(ENXIO)?;
>  /// res.write8(0x42, 0x0);
>  /// # Ok(())
>  /// # }
>  /// ```
> -///
> -/// # Invariants
> -///
> -/// `Self::inner` is guaranteed to be initialized and is always accessed read-only.
> -#[pin_data(PinnedDrop)]
>  pub struct Devres<T: Send> {
>      dev: ARef<Device>,
>      /// Pointer to [`Self::devres_callback`].
> @@ -140,14 +116,7 @@ pub struct Devres<T: Send> {
>      /// Has to be stored, since Rust does not guarantee to always return the same address for a
>      /// function. However, the C API uses the address as a key.
>      callback: unsafe extern "C" fn(*mut c_void),
> -    /// Contains all the fields shared with [`Self::callback`].
> -    // TODO: Replace with `UnsafePinned`, once available.
> -    //
> -    // Subsequently, the `drop_in_place()` in `Devres::drop` and `Devres::new` as well as the
> -    // explicit `Send` and `Sync' impls can be removed.
> -    #[pin]
> -    inner: Opaque<Inner<T>>,
> -    _add_action: (),
> +    data: Arc<Revocable<T>>,
>  }
>  
>  impl<T: Send> Devres<T> {
> @@ -155,74 +124,47 @@ impl<T: Send> Devres<T> {
>      ///
>      /// The `data` encapsulated within the returned `Devres` instance' `data` will be
>      /// (revoked)[`Revocable`] once the device is detached.
> -    pub fn new<'a, E>(
> -        dev: &'a Device<Bound>,
> -        data: impl PinInit<T, E> + 'a,
> -    ) -> impl PinInit<Self, Error> + 'a
> +    pub fn new<E>(dev: &Device<Bound>, data: impl PinInit<T, E>) -> Result<Self>
>      where
> -        T: 'a,
>          Error: From<E>,
>      {
> -        try_pin_init!(&this in Self {
> -            dev: dev.into(),
> -            callback: Self::devres_callback,
> -            // INVARIANT: `inner` is properly initialized.
> -            inner <- Opaque::pin_init(try_pin_init!(Inner {
> -                    devm <- Completion::new(),
> -                    revoke <- Completion::new(),
> -                    data <- Revocable::new(data),
> -            })),
> -            // TODO: Replace with "initializer code blocks" [1] once available.
> -            //
> -            // [1] https://github.com/Rust-for-Linux/pin-init/pull/69
> -            _add_action: {
> -                // SAFETY: `this` is a valid pointer to uninitialized memory.
> -                let inner = unsafe { &raw mut (*this.as_ptr()).inner };
> +        let callback = Self::devres_callback;
> +        let data = Arc::pin_init(Revocable::new(data), GFP_KERNEL)?;
>  
> -                // SAFETY:
> -                // - `dev.as_raw()` is a pointer to a valid bound device.
> -                // - `inner` is guaranteed to be a valid for the duration of the lifetime of `Self`.
> -                // - `devm_add_action()` is guaranteed not to call `callback` until `this` has been
> -                //    properly initialized, because we require `dev` (i.e. the *bound* device) to
> -                //    live at least as long as the returned `impl PinInit<Self, Error>`.
> -                to_result(unsafe {
> -                    bindings::devm_add_action(dev.as_raw(), Some(*callback), inner.cast())
> -                }).inspect_err(|_| {
> -                    let inner = Opaque::cast_into(inner);
> +        // SAFETY:
> +        // - `dev.as_raw()` is a pointer to a valid bound device.
> +        // - `data` is guaranteed to be a valid for the duration of the lifetime of `Self`.
> +        // - `devm_add_action()` is guaranteed not to call `callback` for the entire lifetime of
> +        //   `dev`.
> +        to_result(unsafe {
> +            bindings::devm_add_action(
> +                dev.as_raw(),
> +                Some(callback),
> +                Arc::as_ptr(&data).cast_mut().cast(),
> +            )
> +        })?;
>  
> -                    // SAFETY: `inner` is a valid pointer to an `Inner<T>` and valid for both reads
> -                    // and writes.
> -                    unsafe { core::ptr::drop_in_place(inner) };
> -                })?;
> -            },
> -        })
> -    }
> +        // Take additional reference count for `devm_add_action()`.
> +        core::mem::forget(data.clone());
>  
> -    fn inner(&self) -> &Inner<T> {
> -        // SAFETY: By the type invairants of `Self`, `inner` is properly initialized and always
> -        // accessed read-only.
> -        unsafe { &*self.inner.get() }
> +        Ok(Self {
> +            dev: dev.into(),
> +            callback,
> +            data,
> +        })
>      }
>  
>      fn data(&self) -> &Revocable<T> {
> -        &self.inner().data
> +        &self.data
>      }
>  
>      #[allow(clippy::missing_safety_doc)]
>      unsafe extern "C" fn devres_callback(ptr: *mut kernel::ffi::c_void) {
> -        // SAFETY: In `Self::new` we've passed a valid pointer to `Inner` to `devm_add_action()`,
> -        // hence `ptr` must be a valid pointer to `Inner`.
> -        let inner = unsafe { &*ptr.cast::<Inner<T>>() };
> +        // SAFETY: In `Self::new` we've passed a valid pointer of `Revocable<T>` to
> +        // `devm_add_action()`, hence `ptr` must be a valid pointer to `Revocable<T>`.
> +        let data = unsafe { Arc::from_raw(ptr.cast::<Revocable<T>>()) };
>  
> -        // Ensure that `inner` can't be used anymore after we signal completion of this callback.
> -        let inner = ScopeGuard::new_with_data(inner, |inner| inner.devm.complete_all());
> -
> -        if !inner.data.revoke() {
> -            // If `revoke()` returns false, it means that `Devres::drop` already started revoking
> -            // `data` for us. Hence we have to wait until `Devres::drop` signals that it
> -            // completed revoking `data`.
> -            inner.revoke.wait_for_completion();
> -        }
> +        data.revoke();
>      }
>  
>      fn remove_action(&self) -> bool {
> @@ -234,7 +176,7 @@ fn remove_action(&self) -> bool {
>              bindings::devm_remove_action_nowarn(
>                  self.dev.as_raw(),
>                  Some(self.callback),
> -                core::ptr::from_ref(self.inner()).cast_mut().cast(),
> +                core::ptr::from_ref(self.data()).cast_mut().cast(),
>              )
>          } == 0)
>      }
> @@ -313,31 +255,19 @@ unsafe impl<T: Send> Send for Devres<T> {}
>  // SAFETY: `Devres` can be shared with any task, if `T: Sync`.
>  unsafe impl<T: Send + Sync> Sync for Devres<T> {}
>  
> -#[pinned_drop]
> -impl<T: Send> PinnedDrop for Devres<T> {
> -    fn drop(self: Pin<&mut Self>) {
> +impl<T: Send> Drop for Devres<T> {
> +    fn drop(&mut self) {
>          // SAFETY: When `drop` runs, it is guaranteed that nobody is accessing the revocable data
>          // anymore, hence it is safe not to wait for the grace period to finish.
>          if unsafe { self.data().revoke_nosync() } {
>              // We revoked `self.data` before the devres action did, hence try to remove it.
> -            if !self.remove_action() {
> -                // We could not remove the devres action, which means that it now runs concurrently,
> -                // hence signal that `self.data` has been revoked by us successfully.
> -                self.inner().revoke.complete_all();
> -
> -                // Wait for `Self::devres_callback` to be done using this object.
> -                self.inner().devm.wait_for_completion();
> +            if self.remove_action() {
> +                // SAFETY: In `Self::new` we have taken an additional reference count of `self.data`
> +                // for `devm_add_action()`. Since `remove_action()` was successful, we have to drop
> +                // this additional reference count.
> +                drop(unsafe { Arc::from_raw(Arc::as_ptr(&self.data)) });
>              }
> -        } else {
> -            // `Self::devres_callback` revokes `self.data` for us, hence wait for it to be done
> -            // using this object.
> -            self.inner().devm.wait_for_completion();
>          }
> -
> -        // INVARIANT: At this point it is guaranteed that `inner` can't be accessed any more.
> -        //
> -        // SAFETY: `inner` is valid for dropping.
> -        unsafe { core::ptr::drop_in_place(self.inner.get()) };
>      }
>  }
>  
> 
> base-commit: f55ae0bfa00e446ea751d09f468daeafc303e03f


  reply	other threads:[~2026-02-06  7:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 22:25 [PATCH] rust: devres: fix race condition due to nesting Danilo Krummrich
2026-02-06  7:53 ` Boris Brezillon [this message]
2026-02-06 14:52 ` Greg KH
2026-02-06 15:54 ` Alice Ryhl
2026-02-06 15:56   ` Danilo Krummrich
2026-02-06 16:23     ` Alice Ryhl
2026-02-07  0:15 ` Danilo Krummrich

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=20260206085342.609ab3a1@fedora \
    --to=boris.brezillon@collabora.com \
    --cc=a.hindborg@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=driver-core@lists.linux.dev \
    --cc=gary@garyguo.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=markus.probst@posteo.de \
    --cc=ojeda@kernel.org \
    --cc=rafael@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 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.