From: AI Talking about AI <aitalkingai@gmail.com>
To: rust-for-linux@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] Rust: kernel patch series
Date: Mon, 11 Aug 2025 15:24:12 -0300 [thread overview]
Message-ID: <a7c2ee4a-e9d8-40e9-8695-4bb777d42812@gmail.com> (raw)
In-Reply-To: <42c3fc0c-46a8-4502-ad53-d3b886fad5e8@gmail.com>
From d66384514f12bf7607fbb45185bc66699e6cbf48 Mon Sep 17 00:00:00 2001
From: AI talking about AI <aitalkingai@gmail.com>
Date: Thu, 7 Aug 2025 07:54:00 -0700
Subject: [PATCH 2/2] rust: clarify safety comments in workqueue.rs
Replace placeholder `SAFETY: TODO` comments in rust/kernel/workqueue.rs with detailed explanations of safety invariants for RawWorkItem and WorkItemPointer, following rust kernel guidelines.
Signed-off-by: AI talking about AI <aitalkingai@gmail.com>
---
rust/kernel/workqueue.rs | 29 +++++++++++++++++++++++++++--
1 file changed, 27 insertions(+), 2 deletions(-)
diff --git a/rust/kernel/workqueue.rs b/rust/kernel/workqueue.rs
index b9343d5..4a34651 100644
--- a/rust/kernel/workqueue.rs
+++ b/rust/kernel/workqueue.rs
@@ -881,7 +881,19 @@ where
{
}
-// SAFETY: TODO.
+ // SAFETY:
+ //
+ // The [`run`](WorkItemPointer::run) function pointer stored in the `work_struct` always
+ // originates from a prior call to [`__enqueue`](RawWorkItem::__enqueue) on a
+ // `Pin<KBox<T>>`. A `Pin<KBox<T>>` owns its heap allocation and, by virtue of being
+ // pinned, guarantees that its contents will not be moved. When the C side of the
+ // workqueue invokes the function pointer, it passes back the same `work_struct`
+ // pointer that was produced by `__enqueue`. This implementation computes the
+ // original `KBox` from that pointer via `work_container_of` and converts it back
+ // into a pinned box, which is safe because ownership is transferred back from the
+ // kernel. Therefore, the pointer passed to `run` is always valid for the
+ // duration of the call, and dereferencing it is sound.
+
unsafe impl<T, const ID: u64> WorkItemPointer<ID> for Pin<KBox<T>>
where
T: WorkItem<ID, Pointer = Self>,
@@ -901,7 +913,20 @@ where
}
}
-// SAFETY: TODO.
+ // SAFETY:
+ //
+ // The implementation of [`RawWorkItem::__enqueue`] for `Pin<KBox<T>>` allocates a
+ // new `Work<T, ID>` and obtains a raw pointer to its embedded `work_struct` via
+ // [`raw_get_work`](Work::raw_get). It then passes that pointer to the provided
+ // closure. The `Pin<KBox<T>>` is freshly allocated and by type invariants cannot
+ // already be enqueued, so the closure must return `true`. If it were to return
+ // `false`, the implementation invokes `unreachable_unchecked()`, which is never
+ // reached in valid usage. When the closure returns `true` the C workqueue
+ // subsystem takes ownership of the `work_struct` and will eventually call back
+ // into [`WorkItemPointer::run`], at which point the box is recovered and
+ // dropped. Throughout this process the raw pointer passed to the closure
+ // remains valid for the duration specified in [`RawWorkItem`]'s safety contract.
+
unsafe impl<T, const ID: u64> RawWorkItem<ID> for Pin<KBox<T>>
where
T: WorkItem<ID, Pointer = Self>,
--
2.39.5
next prev parent reply other threads:[~2025-08-11 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 18:20 [PATCH v3 0/2] Rust: kernel patch series AI Talking about AI
2025-08-11 18:22 ` [PATCH v3 1/2] " AI Talking about AI
2025-08-11 18:24 ` AI Talking about AI [this message]
2025-08-12 5:51 ` Greg KH
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=a7c2ee4a-e9d8-40e9-8695-4bb777d42812@gmail.com \
--to=aitalkingai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rust-for-linux@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).