Rust for Linux List
 help / color / mirror / Atom feed
From: "Onur Özkan" <work@onurozkan.dev>
To: Moayad Salloum <salloummoayad4@gmail.com>
Cc: rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
	ojeda@kernel.org, aliceryhl@google.com, lossin@kernel.org,
	a.hindborg@kernel.org
Subject: Re: [PATCH] rust: workqueue: add cancel_work for Arc<T>
Date: Mon, 18 May 2026 08:45:26 +0300	[thread overview]
Message-ID: <20260518054533.4296-1-work@onurozkan.dev> (raw)
In-Reply-To: <20260518042347.95213-1-salloummoayad4@gmail.com>

On Mon, 18 May 2026 07:23:47 +0300
Moayad Salloum <salloummoayad4@gmail.com> wrote:

> Add a safe cancel_work() function for work items owned by Arc<T>.
> 
> In the existing API, enqueueing an Arc<T> calls Arc::into_raw() to leak
> the Arc reference into the workqueue. WorkItemPointer::run() is the only
> place that reclaims it via Arc::from_raw(). Without a cancel function,
> drivers had no safe way to cancel pending work, and any attempt to do so
> by calling bindings::cancel_work() directly would leak the Arc reference
> since run() would never be called.
> 
> cancel_work() handles this by calling Arc::from_raw() when cancel
> succeeds, reclaiming the leaked reference that __enqueue() left behind.
> 
> Signed-off-by: Moayad Salloum <salloummoayad4@gmail.com>
> ---
>  rust/kernel/workqueue.rs | 29 +++++++++++++++++++++++++++++
>  1 file changed, 29 insertions(+)
> 
> diff --git a/rust/kernel/workqueue.rs b/rust/kernel/workqueue.rs
> index 6d665418b..daff9040a 100644
> --- a/rust/kernel/workqueue.rs
> +++ b/rust/kernel/workqueue.rs
> @@ -871,6 +871,35 @@ unsafe fn __enqueue<F>(self, queue_work_on: F) -> Self::EnqueueOutput
>      }
>  }
>  
> +pub fn cancel_work<T, const ID: u64>(item: &Arc<T>) -> bool
> +where
> +    T: WorkItem<ID, Pointer = Arc<T>>,
> +    T: HasWork<T, ID>,
> +{
> +    let ptr = Arc::as_ptr(item);
> +    // SAFETY: `ptr` comes from `Arc::as_ptr` which is a valid non-dangling pointer to `T`.
> +    let work_ptr = unsafe { T::raw_get_work(ptr.cast_mut()) };
> +    // SAFETY: `raw_get_work` returns a pointer to a valid `Work<T, ID>` field.
> +    let work_ptr_struct = unsafe { Work::raw_get(work_ptr) };
> +    // SAFETY: The `Arc` keeps the allocation alive, so `work_ptr_struct` is valid for
> +    // the duration of this call.
> +    let cancel_res = unsafe { bindings::cancel_work(work_ptr_struct) };
> +
> +    if cancel_res {
> +        // SAFETY: `cancel_work` returned true, meaning the work was pending and has been
> +        // removed from the queue. The workqueue will not call `run`, so we are responsible
> +        // for reclaiming the `Arc` reference that was leaked in `__enqueue` via
> +        // `Arc::into_raw`. We use `work_container_of` to recover the original `*const T`
> +        // pointer from the `Work<T, ID>` field pointer, then reconstruct the `Arc` with
> +        // `Arc::from_raw` and drop it to decrement the ref count.
> +        let item_ptr = unsafe { T::work_container_of(work_ptr) };
> +        drop(unsafe { Arc::from_raw(item_ptr) });
> +        true
> +    } else {
> +        false
> +    }
> +}
> +
>  // SAFETY: By the safety requirements of `HasDelayedWork`, the `work_struct` returned by methods in
>  // `HasWork` provides a `work_struct` that is the `work` field of a `delayed_work`, and the rest of
>  // the `delayed_work` has the same access rules as its `work` field.
> -- 
> 2.43.0
> 

[1] already covers this.

- Onur

[1]: https://lore.kernel.org/all/20260510082211.207450-1-work@onurozkan.dev


  reply	other threads:[~2026-05-18  5:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18  4:23 [PATCH] rust: workqueue: add cancel_work for Arc<T> Moayad Salloum
2026-05-18  5:45 ` Onur Özkan [this message]
2026-05-18  8:10 ` kernel test robot
2026-05-18 19:46 ` kernel test robot
  -- strict thread matches above, loose matches on Subject: below --
2026-05-18  4:11 [PATCH 1/2] rust: workqueue: add SAFETY comments for Pin<KBox<T>> impls Moayad Salloum
2026-05-18  4:11 ` [PATCH] rust: workqueue: add cancel_work for Arc<T> Moayad Salloum

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=20260518054533.4296-1-work@onurozkan.dev \
    --to=work@onurozkan.dev \
    --cc=a.hindborg@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=salloummoayad4@gmail.com \
    /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