From: Benno Lossin <benno.lossin@proton.me>
To: "Antonio Hickey" <contact@antoniohickey.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>
Cc: rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 10/17] rust: workqueue: replace `raw_get` with pointer cast
Date: Sun, 23 Mar 2025 10:38:17 +0000 [thread overview]
Message-ID: <D8NKWUQK703Y.38SYPI7LCXKO3@proton.me> (raw)
On Thu Mar 20, 2025 at 3:07 AM CET, Antonio Hickey wrote:
> Now that `Work` is initialized via `pin-init`, the `work` field
> is always used. This allows us to replace the use of unsafe
> `Opaque::raw_get` with direct pointer casting.
>
> Suggested-by: Boqun Feng <boqun.feng@gmail.com>
> Link: https://lore.kernel.org/all/20250316061429.817126-1-contact@antoniohickey.com/T/#mc7a4757e8c132f84228b728c7d123d73841501d6
> Signed-off-by: Antonio Hickey <contact@antoniohickey.com>
One nit below, but regardless:
Reviewed-by: Benno Lossin <benno.lossin@proton.me>
> ---
> rust/kernel/workqueue.rs | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/rust/kernel/workqueue.rs b/rust/kernel/workqueue.rs
> index 4e27df324d26..5cc259c1e502 100644
> --- a/rust/kernel/workqueue.rs
> +++ b/rust/kernel/workqueue.rs
> @@ -399,12 +399,8 @@ pub fn new(name: &'static CStr, key: &'static LockClassKey) -> impl PinInit<Self
> /// need not be initialized.)
> #[inline]
> pub unsafe fn raw_get(ptr: *const Self) -> *mut bindings::work_struct {
> - // SAFETY: The caller promises that the pointer is aligned and not dangling.
> - //
> - // A pointer cast would also be ok due to `#[repr(transparent)]`. We use
> - // `&raw const (*ptr).work` so that the compiler does not complain that the
> - // `work` field is unused.
> - unsafe { Opaque::raw_get(&raw const (*ptr).work) }
> + // CAST: `Work` is transparent to `bindings::work_struct`.
I usually write:
// CAST: `Work` is transparently wrapping `bindings::work_struct`.
So feel free to use that. (I find the "transparent to" a bit strange,
but this isn't a huge complaint)
---
Cheers,
Benno
> + ptr.cast_mut().cast()
> }
> }
>
next reply other threads:[~2025-03-23 10:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-23 10:38 Benno Lossin [this message]
[not found] <20250320020740.1631171-1-contact@antoniohickey.com>
2025-03-20 2:07 ` Antonio Hickey
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=D8NKWUQK703Y.38SYPI7LCXKO3@proton.me \
--to=benno.lossin@proton.me \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=contact@antoniohickey.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®