From: Boqun Feng <boqun.feng@gmail.com>
To: Benno Lossin <benno.lossin@proton.me>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Andreas Hindborg" <a.hindborg@samsung.com>,
"Alice Ryhl" <aliceryhl@google.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] rust: kernel: add `drop_contents` to `BoxExt`
Date: Mon, 19 Aug 2024 10:23:49 -0700 [thread overview]
Message-ID: <ZsN_pbvd45Gij66O@boqun-archlinux> (raw)
In-Reply-To: <20240819112415.99810-1-benno.lossin@proton.me>
On Mon, Aug 19, 2024 at 11:24:35AM +0000, Benno Lossin wrote:
> Sometimes (see [1]) it is necessary to drop the value inside of a
> `Box<T>`, but retain the allocation. For example to reuse the allocation
> in the future.
> Introduce a new function `drop_contents` that turns a `Box<T>` into
> `Box<MaybeUninit<T>>` by dropping the value.
>
> Signed-off-by: Benno Lossin <benno.lossin@proton.me>
> Link: https://lore.kernel.org/rust-for-linux/20240418-b4-rbtree-v3-5-323e134390ce@google.com/ [1]
Reviewed-by: Boqun Feng <boqun.feng@gmail.com>
Regards,
Boqun
> ---
> rust/kernel/alloc/box_ext.rs | 31 ++++++++++++++++++++++++++++++-
> 1 file changed, 30 insertions(+), 1 deletion(-)
>
> diff --git a/rust/kernel/alloc/box_ext.rs b/rust/kernel/alloc/box_ext.rs
> index 829cb1c1cf9e..b68ade26a42d 100644
> --- a/rust/kernel/alloc/box_ext.rs
> +++ b/rust/kernel/alloc/box_ext.rs
> @@ -4,7 +4,7 @@
>
> use super::{AllocError, Flags};
> use alloc::boxed::Box;
> -use core::mem::MaybeUninit;
> +use core::{mem::MaybeUninit, ptr, result::Result};
>
> /// Extensions to [`Box`].
> pub trait BoxExt<T>: Sized {
> @@ -17,6 +17,22 @@ pub trait BoxExt<T>: Sized {
> ///
> /// The allocation may fail, in which case an error is returned.
> fn new_uninit(flags: Flags) -> Result<Box<MaybeUninit<T>>, AllocError>;
> +
> + /// Drops the contents, but keeps the allocation.
> + ///
> + /// # Examples
> + ///
> + /// ```
> + /// use kernel::alloc::{flags, box_ext::BoxExt};
> + /// let value = Box::new([0; 32], flags::GFP_KERNEL)?;
> + /// assert_eq!(*value, [0; 32]);
> + /// let value = Box::drop_contents(value);
> + /// // Now we can re-use `value`:
> + /// let value = Box::write(value, [1; 32]);
> + /// assert_eq!(*value, [1; 32]);
> + /// # Ok::<(), Error>(())
> + /// ```
> + fn drop_contents(this: Self) -> Box<MaybeUninit<T>>;
> }
>
> impl<T> BoxExt<T> for Box<T> {
> @@ -53,4 +69,17 @@ fn new_uninit(flags: Flags) -> Result<Box<MaybeUninit<T>>, AllocError> {
> // zero-sized types, we use `NonNull::dangling`.
> Ok(unsafe { Box::from_raw(ptr) })
> }
> +
> + fn drop_contents(this: Self) -> Box<MaybeUninit<T>> {
> + let ptr = Box::into_raw(this);
> + // SAFETY: `ptr` is valid, because it came from `Box::into_raw`.
> + unsafe { ptr::drop_in_place(ptr) };
> +
> + // CAST: `MaybeUninit<T>` is a transparent wrapper of `T`.
> + let ptr = ptr.cast::<MaybeUninit<T>>();
> +
> + // SAFETY: `ptr` is valid for writes, because it came from `Box::into_raw` and it is valid for
> + // reads, since the pointer came from `Box::into_raw` and the type is `MaybeUninit<T>`.
> + unsafe { Box::from_raw(ptr) }
> + }
> }
>
> base-commit: c4d7f546dd9aa9780716cdb07416ca97264dce43
> --
> 2.45.2
>
>
>
next prev parent reply other threads:[~2024-08-19 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 11:24 [PATCH v4 1/2] rust: kernel: add `drop_contents` to `BoxExt` Benno Lossin
2024-08-19 11:24 ` [PATCH v4 2/2] rust: init: add `write_[pin_]init` functions Benno Lossin
2024-08-19 11:36 ` Alice Ryhl
2024-08-19 17:24 ` Boqun Feng
2024-08-19 11:33 ` [PATCH v4 1/2] rust: kernel: add `drop_contents` to `BoxExt` Alice Ryhl
2024-08-19 17:23 ` Boqun Feng [this message]
2024-08-21 22:16 ` 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=ZsN_pbvd45Gij66O@boqun-archlinux \
--to=boqun.feng@gmail.com \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--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).