From: Benno Lossin <y86-dev@protonmail.com>
To: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Alice Ryhl" <alice@ryhl.io>,
"Andreas Hindborg" <nmi@metaspace.dk>
Cc: rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@lists.linux.dev, Benno Lossin <y86-dev@protonmail.com>,
Wedson Almeida Filho <walmeida@microsoft.com>,
Andreas Hindborg <a.hindborg@samsung.com>,
Alice Ryhl <aliceryhl@google.com>
Subject: [PATCH v7 04/15] rust: sync: add `assume_init` to `UniqueArc`
Date: Sat, 08 Apr 2023 12:25:34 +0000 [thread overview]
Message-ID: <20230408122429.1103522-5-y86-dev@protonmail.com> (raw)
In-Reply-To: <20230408122429.1103522-1-y86-dev@protonmail.com>
Adds the `assume_init` function to `UniqueArc<MaybeUninit<T>>` that
unsafely assumes the value to be initialized and yields a value of type
`UniqueArc<T>`. This function is used when manually initializing the
pointee of an `UniqueArc`.
Signed-off-by: Benno Lossin <y86-dev@protonmail.com>
Reviewed-by: Wedson Almeida Filho <walmeida@microsoft.com>
Reviewed-by: Andreas Hindborg <a.hindborg@samsung.com>
Reviewed-by: Alice Ryhl <aliceryhl@google.com>
---
rust/kernel/sync/arc.rs | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/rust/kernel/sync/arc.rs b/rust/kernel/sync/arc.rs
index aa7135f0f238..eee7008e5e3e 100644
--- a/rust/kernel/sync/arc.rs
+++ b/rust/kernel/sync/arc.rs
@@ -489,6 +489,17 @@ impl<T> UniqueArc<MaybeUninit<T>> {
/// Converts a `UniqueArc<MaybeUninit<T>>` into a `UniqueArc<T>` by writing a value into it.
pub fn write(mut self, value: T) -> UniqueArc<T> {
self.deref_mut().write(value);
+ // SAFETY: We just wrote the value to be initialized.
+ unsafe { self.assume_init() }
+ }
+
+ /// Unsafely assume that `self` is initialized.
+ ///
+ /// # Safety
+ ///
+ /// The caller guarantees that the value behind this pointer has been initialized. It is
+ /// *immediate* UB to call this when the value is not initialized.
+ pub unsafe fn assume_init(self) -> UniqueArc<T> {
let inner = ManuallyDrop::new(self).inner.ptr;
UniqueArc {
// SAFETY: The new `Arc` is taking over `ptr` from `self.inner` (which won't be
--
2.39.2
next prev parent reply other threads:[~2023-04-08 12:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 12:25 [PATCH v7 00/15] Rust pin-init API for pinned initialization of structs Benno Lossin
2023-04-08 12:25 ` [PATCH v7 01/15] rust: enable the `pin_macro` feature Benno Lossin
2023-04-08 12:25 ` [PATCH v7 02/15] rust: macros: add `quote!` macro Benno Lossin
2023-04-08 12:25 ` [PATCH v7 03/15] rust: sync: change error type of constructor functions Benno Lossin
2023-04-08 12:25 ` Benno Lossin [this message]
2023-04-08 12:25 ` [PATCH v7 05/15] rust: types: add `Opaque::raw_get` Benno Lossin
2023-04-08 12:25 ` [PATCH v7 06/15] rust: add pin-init API core Benno Lossin
2023-04-08 12:25 ` [PATCH v7 07/15] rust: init: add initialization macros Benno Lossin
2023-04-08 12:25 ` [PATCH v7 08/15] rust: init/sync: add `InPlaceInit` trait to pin-initialize smart pointers Benno Lossin
2023-04-08 12:26 ` [PATCH v7 09/15] rust: init: add `PinnedDrop` trait and macros Benno Lossin
2023-04-08 12:26 ` [PATCH v7 10/15] rust: init: add `stack_pin_init!` macro Benno Lossin
2023-04-08 12:26 ` [PATCH v7 11/15] rust: init: add `Zeroable` trait and `init::zeroed` function Benno Lossin
2023-04-08 12:26 ` [PATCH v7 12/15] rust: prelude: add `pin-init` API items to prelude Benno Lossin
2023-04-08 12:26 ` [PATCH v7 13/15] rust: types: add `Opaque::ffi_init` Benno Lossin
2023-04-08 15:21 ` Andreas Hindborg
2023-04-11 8:12 ` Alice Ryhl
2023-04-08 12:26 ` [PATCH v7 14/15] rust: sync: reduce stack usage of `UniqueArc::try_new_uninit` Benno Lossin
2023-04-08 12:26 ` [PATCH v7 15/15] rust: sync: add functions for initializing `UniqueArc<MaybeUninit<T>>` Benno Lossin
2023-04-10 22:54 ` [PATCH v7 00/15] Rust pin-init API for pinned initialization of structs Miguel Ojeda
2023-04-12 20:13 ` y86-dev
2023-04-12 20:15 ` Miguel Ojeda
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=20230408122429.1103522-5-y86-dev@protonmail.com \
--to=y86-dev@protonmail.com \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=alice@ryhl.io \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nmi@metaspace.dk \
--cc=ojeda@kernel.org \
--cc=patches@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=walmeida@microsoft.com \
--cc=wedsonaf@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;
as well as URLs for NNTP newsgroup(s).