From: Christian Schrefl <chrisi.schrefl@gmail.com>
To: Sky <sky@sky9.dev>, "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>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Gerald Wisböck" <gerald.wisboeck@feather.ink>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <nick.desaulniers+lkml@gmail.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>
Cc: linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
llvm@lists.linux.dev,
Christian Schrefl <chrisi.schrefl@gmail.com>,
Benno Lossin <lossin@kernel.org>
Subject: [PATCH v3 3/3] rust: use `UnsafePinned` in the implementation of `Opaque`
Date: Sat, 10 May 2025 11:32:28 +0200 [thread overview]
Message-ID: <20250510-rust_unsafe_pinned-v3-3-57ce151123f9@gmail.com> (raw)
In-Reply-To: <20250510-rust_unsafe_pinned-v3-0-57ce151123f9@gmail.com>
Make the semantics of the `Opaque` implementation clearer and prepare
for the switch to the upstream rust `UnsafePinned` type in the future.
`Opaque` still uses `UnsafeCell` even though the kernel implementation
of `UnsafePinned` already includes it, since the current upstream
version does not.
Reviewed-by: Gerald Wisböck <gerald.wisboeck@feather.ink>
Reviewed-by: Alice Ryhl <aliceryhl@google.com>
Reviewed-by: Benno Lossin <lossin@kernel.org>
Signed-off-by: Christian Schrefl <chrisi.schrefl@gmail.com>
---
rust/kernel/types.rs | 32 +++++++++++++++-----------------
1 file changed, 15 insertions(+), 17 deletions(-)
diff --git a/rust/kernel/types.rs b/rust/kernel/types.rs
index f06e8720e012102e5c41e79fd97b0607e927d71c..e32905c42453132fbea49d37a6457547d42465ce 100644
--- a/rust/kernel/types.rs
+++ b/rust/kernel/types.rs
@@ -4,12 +4,12 @@
use core::{
cell::UnsafeCell,
- marker::{PhantomData, PhantomPinned},
+ marker::PhantomData,
mem::{ManuallyDrop, MaybeUninit},
ops::{Deref, DerefMut},
ptr::NonNull,
};
-use pin_init::{PinInit, Wrapper, Zeroable};
+use pin_init::{cast_pin_init, PinInit, Wrapper, Zeroable};
/// Used to transfer ownership to and from foreign (non-Rust) languages.
///
@@ -308,8 +308,10 @@ fn drop(&mut self) {
/// ```
#[repr(transparent)]
pub struct Opaque<T> {
- value: UnsafeCell<MaybeUninit<T>>,
- _pin: PhantomPinned,
+ // The kernel implementation of `UnsafePinned` uses `UnsafeCell` internally, but the
+ // upstream rust `UnsafePinned` will not. So to make sure this is compatible with
+ // the upstream version use `UnsafeCell` here.
+ value: UnsafePinned<UnsafeCell<MaybeUninit<T>>>,
}
// SAFETY: `Opaque<T>` allows the inner value to be any bit pattern, including all zeros.
@@ -319,16 +321,14 @@ impl<T> Opaque<T> {
/// Creates a new opaque value.
pub const fn new(value: T) -> Self {
Self {
- value: UnsafeCell::new(MaybeUninit::new(value)),
- _pin: PhantomPinned,
+ value: UnsafePinned::new(UnsafeCell::new(MaybeUninit::new(value))),
}
}
/// Creates an uninitialised value.
pub const fn uninit() -> Self {
Self {
- value: UnsafeCell::new(MaybeUninit::uninit()),
- _pin: PhantomPinned,
+ value: UnsafePinned::new(UnsafeCell::new(MaybeUninit::uninit())),
}
}
@@ -371,7 +371,7 @@ pub fn try_ffi_init<E>(
/// Returns a raw pointer to the opaque data.
pub const fn get(&self) -> *mut T {
- UnsafeCell::get(&self.value).cast::<T>()
+ UnsafeCell::raw_get(self.value.get()).cast::<T>()
}
/// Gets the value behind `this`.
@@ -384,14 +384,12 @@ pub const fn raw_get(this: *const Self) -> *mut T {
}
impl<T> Wrapper<T> for Opaque<T> {
/// Create an opaque pin-initializer from the given pin-initializer.
- fn pin_init<E>(slot: impl PinInit<T, E>) -> impl PinInit<Self, E> {
- Self::try_ffi_init(|ptr: *mut T| {
- // SAFETY:
- // - `ptr` is a valid pointer to uninitialized memory,
- // - `slot` is not accessed on error; the call is infallible,
- // - `slot` is pinned in memory.
- unsafe { PinInit::<T, E>::__pinned_init(slot, ptr) }
- })
+ fn pin_init<E>(value_init: impl PinInit<T, E>) -> impl PinInit<Self, E> {
+ let value_init =
+ UnsafePinned::pin_init(UnsafeCell::pin_init(MaybeUninit::pin_init(value_init)));
+ // SAFETY: `Opaque<T>` is a `repr(transparent)` wrapper around
+ // `UnsafePinned<UnsafeCell<MabeUninit<T>>>` so the memory representation is compatible.
+ unsafe { cast_pin_init(value_init) }
}
}
--
2.49.0
prev parent reply other threads:[~2025-05-10 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-10 9:32 [PATCH v3 0/3] rust: add `UnsafePinned` type Christian Schrefl
2025-05-10 9:32 ` [PATCH v3 1/3] rust: add UnsafePinned type Christian Schrefl
2025-05-11 12:16 ` kernel test robot
2025-05-10 9:32 ` [PATCH v3 2/3] rust: implement `Wrapper<T>` for `Opaque<T>` Christian Schrefl
2025-05-10 9:32 ` Christian Schrefl [this message]
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=20250510-rust_unsafe_pinned-v3-3-57ce151123f9@gmail.com \
--to=chrisi.schrefl@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=gerald.wisboeck@feather.ink \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=lossin@kernel.org \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sky@sky9.dev \
--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;
as well as URLs for NNTP newsgroup(s).