rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benno Lossin <benno.lossin@proton.me>
To: Boqun Feng <boqun.feng@gmail.com>
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 v2 1/2] rust: kernel: add `drop_contents` to `BoxExt`
Date: Wed, 17 Jul 2024 19:54:14 +0000	[thread overview]
Message-ID: <323ad3d0-e478-4ed9-875c-335ced829afd@proton.me> (raw)
In-Reply-To: <Zoxfjfl9Izaz2Wtj@boqun-archlinux>

On 08.07.24 23:52, Boqun Feng wrote:
> On Mon, Jul 08, 2024 at 02:14:50PM -0700, Boqun Feng wrote:
>> On Mon, Jul 08, 2024 at 08:53:38PM +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]
>>> ---
>>>  rust/kernel/alloc/box_ext.rs | 21 +++++++++++++++++++++
>>>  1 file changed, 21 insertions(+)
>>>
>>> diff --git a/rust/kernel/alloc/box_ext.rs b/rust/kernel/alloc/box_ext.rs
>>> index cdbb5ad166d9..6cf79f96d6c7 100644
>>> --- a/rust/kernel/alloc/box_ext.rs
>>> +++ b/rust/kernel/alloc/box_ext.rs
>>> @@ -5,6 +5,7 @@
>>>  use super::{AllocError, Flags};
>>>  use alloc::boxed::Box;
>>>  use core::mem::MaybeUninit;
>>> +use core::ptr;
>>>  use core::result::Result;
>>>
>>>  /// Extensions to [`Box`].
>>> @@ -18,6 +19,18 @@ 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.
>>> +    ///
> 
> (I spoke too soon ;-))
> 
>>> +    /// # Examples
>>> +    ///
>>> +    /// ```
> 
> need a `use` here:
> 
> 	use kernel::alloc::{flags, box_ext::BoxExt};

Oops, should have checked that.

>>> +    /// let value = Box::new([0; 32], flags::GFP_KERNEL)
> 
> missing a '?' and a ';' at the end of this line.
> 
>>> +    /// let value = value.drop_contents();
>>> +    /// // Now we can re-use `value`:
>>> +    /// Box::write(value, [1; 32]);
> 
> Need a line:
> 
> 	# Ok::<(), Error>(())
> 
> here.
>>> +    /// ```
>>> +    fn drop_contents(self) -> Box<MaybeUninit<T>>;
>>>  }
>>>
> [...]
> 
> I queued this patch in rust-dev with these fixes applied, FYI.

Thanks!

@Miguel, when you take this, then apply the fixes that Boqun suggested.

---
Cheers,
Benno


  reply	other threads:[~2024-07-17 19:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-08 20:53 [PATCH v2 1/2] rust: kernel: add `drop_contents` to `BoxExt` Benno Lossin
2024-07-08 20:53 ` [PATCH v2 2/2] rust: init: add `write_[pin_]init` functions Benno Lossin
2024-07-08 21:27   ` Boqun Feng
2024-08-01  9:02   ` Alice Ryhl
2024-08-01 12:30   ` Gary Guo
2024-07-08 21:14 ` [PATCH v2 1/2] rust: kernel: add `drop_contents` to `BoxExt` Boqun Feng
2024-07-08 21:52   ` Boqun Feng
2024-07-17 19:54     ` Benno Lossin [this message]
2024-08-01  9:01 ` Alice Ryhl

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=323ad3d0-e478-4ed9-875c-335ced829afd@proton.me \
    --to=benno.lossin@proton.me \
    --cc=a.hindborg@samsung.com \
    --cc=alex.gaynor@gmail.com \
    --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=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).