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 v3 1/2] rust: kernel: add `drop_contents` to `BoxExt`
Date: Sat, 3 Aug 2024 08:40:04 -0700 [thread overview]
Message-ID: <Zq5PVEZNcXHThNHB@boqun-archlinux> (raw)
In-Reply-To: <7a145166-cfe0-48b0-994b-6c6a4ff6744b@proton.me>
On Sat, Aug 03, 2024 at 03:32:06PM +0000, Benno Lossin wrote:
> On 03.08.24 17:11, Boqun Feng wrote:
> > On Sat, Aug 03, 2024 at 02:23:42PM +0000, Benno Lossin wrote:
> >> On 03.08.24 16:16, Benno Lossin wrote:
> >>> @@ -53,4 +69,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(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) };
> >>> + // SAFETY: `ptr` is valid, because it came from `Box::into_raw`.
> >>
> >> I just noticed that I missed another comment from Boqun here. Got
> >> confused with the two mails. I would replace the comment above with
> >>
> >> // CAST: `T` and `MaybeUninit<T>` have the same layout.
> >> 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>`.
> >>
> >> Let me know if you want another version.
> >
> > Looks good to me, please do send an updated version.
> >
> > Although, I would expect the "CAST" comment already explains that if
> > `ptr` is a valid, then the casting result is also valid, i.e. we put
> > "CAST" comments on the casting that matters to safety. But that seems
> > not matching what you use CAST for?
>
> Well the pointer is no longer valid for reads, since the value has been
> dropped. Only through the cast, it becomes again read-valid.
>
Fair enough, the past Boqun who made that suggestion might also realise
this and that's why he brought this up ;-)
> CAST comments must justify why the layouts are the same. On that note,
> this comment might be better:
>
> // CAST: `MaybeUninit<T>` is a transparent wrapper of `T`.
>
Looks good to me.
Regards,
Boqun
> ---
> Cheers,
> Benno
>
next prev parent reply other threads:[~2024-08-03 15:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-03 14:16 [PATCH v3 1/2] rust: kernel: add `drop_contents` to `BoxExt` Benno Lossin
2024-08-03 14:17 ` [PATCH v3 2/2] rust: init: add `write_[pin_]init` functions Benno Lossin
2024-08-03 14:23 ` [PATCH v3 1/2] rust: kernel: add `drop_contents` to `BoxExt` Benno Lossin
2024-08-03 15:11 ` Boqun Feng
2024-08-03 15:32 ` Benno Lossin
2024-08-03 15:40 ` Boqun Feng [this message]
2024-08-03 23:22 ` Danilo Krummrich
2024-08-05 8:43 ` Alice Ryhl
2024-08-05 9:07 ` Danilo Krummrich
2024-08-05 20:39 ` Benno Lossin
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=Zq5PVEZNcXHThNHB@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).