From: "Benno Lossin" <lossin@kernel.org>
To: "Alexandre Courbot" <acourbot@nvidia.com>,
"Abdiel Janulgue" <abdiel.janulgue@gmail.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Robin Murphy" <robin.murphy@arm.com>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>
Cc: "Christian S. Lima" <christiansantoslima21@gmail.com>,
<rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] rust: transmute: add `as_bytes` method for `AsBytes` trait
Date: Sat, 26 Jul 2025 10:49:12 +0200 [thread overview]
Message-ID: <DBLUVHKRGVCO.19XQMAX6S1M7W@kernel.org> (raw)
In-Reply-To: <20250726-as_bytes-v3-1-eb7514faab28@nvidia.com>
On Sat Jul 26, 2025 at 4:47 AM CEST, Alexandre Courbot wrote:
> Every type that implements `AsBytes` should be able to provide its byte
> representation. Introduce the `as_bytes` method that returns the
> implementer as a stream of bytes, and provide a default implementation
> that should be suitable for any type that satisfies `AsBytes`'s safety
> requirements.
>
> Reviewed-by: Danilo Krummrich <dakr@kernel.org>
> Signed-off-by: Alexandre Courbot <acourbot@nvidia.com>
Reviewed-by: Benno Lossin <lossin@kernel.org>
> ---
> This is the sister patch of [1], providing an `as_bytes` method for
> `AsBytes`.
>
> It is going to be used in Nova, but should also be universally useful -
> if anything, it felt a bit strange that `AsBytes` did not provide this
> method so far.
>
> [1] https://lore.kernel.org/rust-for-linux/20250624042802.105623-1-christiansantoslima21@gmail.com/
> ---
> Changes in v3:
> - Use `ptr::from_ref` instead of `as *const T`.
> - Link to v2: https://lore.kernel.org/r/20250725-as_bytes-v2-1-c6584c211a6c@nvidia.com
>
> Changes in v2:
> - Use `size_of_val` to provide a default implementation for both `Sized`
> and non-`Sized` types, and remove `AsBytesSized`. (thanks Alice!)
> - Link to v1: https://lore.kernel.org/r/20250725-as_bytes-v1-1-6f06a3744f69@nvidia.com
> ---
> rust/kernel/transmute.rs | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/rust/kernel/transmute.rs b/rust/kernel/transmute.rs
> index 1c7d43771a37b90150de86699f114a2ffb84db91..69c46c19a89191d8a2abc5801564cacda232218c 100644
> --- a/rust/kernel/transmute.rs
> +++ b/rust/kernel/transmute.rs
> @@ -47,7 +47,16 @@ macro_rules! impl_frombytes {
> ///
> /// Values of this type may not contain any uninitialized bytes. This type must not have interior
> /// mutability.
> -pub unsafe trait AsBytes {}
> +pub unsafe trait AsBytes {
> + /// Returns `self` as a slice of bytes.
> + fn as_bytes(&self) -> &[u8] {
> + let data = core::ptr::from_ref(self).cast::<u8>();
> + let len = size_of_val(self);
> +
> + // SAFETY: `data` is non-null and valid for `len * sizeof::<u8>()` bytes.
> + unsafe { core::slice::from_raw_parts(data, len) }
> + }
> +}
>
> macro_rules! impl_asbytes {
> ($($({$($generics:tt)*})? $t:ty, )*) => {
>
> ---
> base-commit: 14ae91a81ec8fa0bc23170d4aa16dd2a20d54105
Normally I'd expect this to be `rust-next` or an `-rc` tag... I did find
this in one of the trees that I fetch, so no worries, but maybe in the
future use one of those? Thanks!
---
Cheers,
Benno
> change-id: 20250725-as_bytes-6cbc11f2e8c3
>
> Best regards,
next prev parent reply other threads:[~2025-07-26 8:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-26 2:47 [PATCH v3] rust: transmute: add `as_bytes` method for `AsBytes` trait Alexandre Courbot
2025-07-26 8:49 ` Benno Lossin [this message]
2025-07-27 6:52 ` Alice Ryhl
2025-07-27 10:23 ` Alice Ryhl
2025-07-27 12:39 ` Benno Lossin
2025-07-27 15:21 ` Alice Ryhl
2025-07-28 3:39 ` Alexandre Courbot
2025-07-28 9:09 ` Benno Lossin
2025-07-28 10:01 ` Danilo Krummrich
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=DBLUVHKRGVCO.19XQMAX6S1M7W@kernel.org \
--to=lossin@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=abdiel.janulgue@gmail.com \
--cc=acourbot@nvidia.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=christiansantoslima21@gmail.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.