From: Gary Guo <gary@garyguo.net>
To: Matt Gilbride <mattgilbride@google.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@samsung.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Arve Hjønnevåg" <arve@android.com>,
"Todd Kjos" <tkjos@android.com>,
"Martijn Coenen" <maco@android.com>,
"Joel Fernandes" <joel@joelfernandes.org>,
"Carlos Llamas" <cmllamas@google.com>,
"Suren Baghdasaryan" <surenb@google.com>,
"Christian Brauner" <brauner@kernel.org>,
"Rob Landley" <rob@landley.net>,
"Davidlohr Bueso" <dave@stgolabs.net>,
"Michel Lespinasse" <michel@lespinasse.org>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 1/6] rust: kernel: add `drop_contents` to `BoxExt`
Date: Wed, 31 Jul 2024 21:02:06 +0100 [thread overview]
Message-ID: <20240731210206.2b56b432.gary@garyguo.net> (raw)
In-Reply-To: <20240711-b4-rbtree-v6-1-14bef1a8cdba@google.com>
On Thu, 11 Jul 2024 16:20:57 +0000
Matt Gilbride <mattgilbride@google.com> wrote:
> From: Benno Lossin <benno.lossin@proton.me>
>
> 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]
> ---
> rust/kernel/alloc/box_ext.rs | 24 +++++++++++++++++++++++-
> 1 file changed, 23 insertions(+), 1 deletion(-)
>
> diff --git a/rust/kernel/alloc/box_ext.rs b/rust/kernel/alloc/box_ext.rs
> index 829cb1c1cf9e..557895db4f48 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};
>
> /// Extensions to [`Box`].
> pub trait BoxExt<T>: Sized {
> @@ -17,6 +17,20 @@ 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;
> + ///
> + /// let value = Box::new([0; 32], flags::GFP_KERNEL);
> + /// let value = value.unwrap().drop_contents();
> + /// // Now we can re-use `value`:
> + /// Box::write(value, [1; 32]);
> + /// ```
> + fn drop_contents(self) -> Box<MaybeUninit<T>>;
Should this have signature `fn drop_contents(this: Self) -> ...`? Box
types normally don't have methods to avoid shadowing functions that the
pointee may have.
> }
>
> impl<T> BoxExt<T> for Box<T> {
> @@ -53,4 +67,12 @@ 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(self) -> Box<MaybeUninit<T>> {
> + let ptr = Box::into_raw(self);
> + // SAFETY: `ptr` is valid, because it came from `Box::into_raw`.
> + unsafe { ptr::drop_in_place(ptr) };
> + // SAFETY: `ptr` is valid, because it came from `Box::into_raw`.
> + unsafe { Box::from_raw(ptr.cast()) }
> + }
> }
>
Best,
Gary
next prev parent reply other threads:[~2024-07-31 20:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 16:20 [PATCH v6 0/6] Red-black tree abstraction needed by Rust Binder Matt Gilbride
2024-07-11 16:20 ` [PATCH v6 1/6] rust: kernel: add `drop_contents` to `BoxExt` Matt Gilbride
2024-07-23 9:15 ` Alice Ryhl
2024-07-31 20:02 ` Gary Guo [this message]
2024-07-31 20:47 ` Benno Lossin
2024-08-03 12:24 ` Miguel Ojeda
2024-07-11 16:20 ` [PATCH v6 2/6] rust: rbtree: add red-black tree implementation backed by the C version Matt Gilbride
2024-07-11 16:20 ` [PATCH v6 3/6] rust: rbtree: add iterator Matt Gilbride
2024-07-11 16:21 ` [PATCH v6 4/6] rust: rbtree: add mutable iterator Matt Gilbride
2024-07-11 16:21 ` [PATCH v6 5/6] rust: rbtree: add `RBTreeCursor` Matt Gilbride
2024-07-11 16:21 ` [PATCH v6 6/6] rust: rbtree: add `RBTree::entry` Matt Gilbride
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=20240731210206.2b56b432.gary@garyguo.net \
--to=gary@garyguo.net \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=arve@android.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=brauner@kernel.org \
--cc=cmllamas@google.com \
--cc=dave@stgolabs.net \
--cc=gregkh@linuxfoundation.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maco@android.com \
--cc=mattgilbride@google.com \
--cc=michel@lespinasse.org \
--cc=ojeda@kernel.org \
--cc=rob@landley.net \
--cc=rust-for-linux@vger.kernel.org \
--cc=surenb@google.com \
--cc=tkjos@android.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).