From: "Gary Guo" <gary@garyguo.net>
To: "Andreas Hindborg" <a.hindborg@kernel.org>,
"Danilo Krummrich" <dakr@kernel.org>, <aliceryhl@google.com>,
<acourbot@nvidia.com>, <ojeda@kernel.org>, <boqun@kernel.org>,
<gary@garyguo.net>, <bjorn3_gh@protonmail.com>,
<lossin@kernel.org>, <tmgross@umich.edu>,
<abdiel.janulgue@gmail.com>, <daniel.almeida@collabora.com>,
<robin.murphy@arm.com>
Cc: <driver-core@lists.linux.dev>, <nouveau@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>,
<rust-for-linux@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/8] rust: dma: add generalized container for types other than slices
Date: Tue, 24 Mar 2026 14:06:01 +0000 [thread overview]
Message-ID: <DHB2JCKXZ5ZN.LA5E3HY3YHGS@garyguo.net> (raw)
In-Reply-To: <877br1qr6v.fsf@kernel.org>
On Tue Mar 24, 2026 at 1:42 PM GMT, Andreas Hindborg wrote:
> "Danilo Krummrich" <dakr@kernel.org> writes:
>
>> + /// Returns a reference to the data in the region.
>> ///
>> - /// # Examples
>> + /// # Safety
>> ///
>> - /// ```
>> - /// # use kernel::device::{Bound, Device};
>> - /// use kernel::dma::{attrs::*, CoherentAllocation};
>> + /// * Callers must ensure that the device does not read/write to/from memory while the returned
>> + /// slice is live.
>> + /// * Callers must ensure that this call does not race with a write to the same region while
>> + /// the returned slice is live.
>> + #[inline]
>> + pub unsafe fn as_ref(&self) -> &T {
>> + // SAFETY: per safety requirement.
>
> Is this enough? Don't you need to assert a valid bit pattern? I assume
> you get this from `FromBytes`, but that bound is not on `T` in this impl
> block.
Concetually `Coherent<T>` is a container of `T` so it should always hold a valid
bit pattern for the type. Perhaps this should be added to the type invariant.
FromBytes is only needed at the constructor level as that's the only place where
you're asserting that initial bit pattern is valid.
>
>> + unsafe { &*self.as_ptr() }
>> + }
>> +
>> + /// Returns a mutable reference to the data in the region.
>> ///
>> - /// # fn test(dev: &Device<Bound>) -> Result {
>> - /// let c: CoherentAllocation<u64> =
>> - /// CoherentAllocation::alloc_attrs(dev, 4, GFP_KERNEL, DMA_ATTR_NO_WARN)?;
>> - /// # Ok::<(), Error>(()) }
>> - /// ```
>> - pub fn alloc_attrs(
>> + /// # Safety
>> + ///
>> + /// * Callers must ensure that the device does not read/write to/from memory while the returned
>> + /// slice is live.
>> + /// * Callers must ensure that this call does not race with a read or write to the same region
>> + /// while the returned slice is live.
>> + #[expect(clippy::mut_from_ref, reason = "unsafe to use API")]
>> + #[inline]
>> + pub unsafe fn as_mut(&self) -> &mut T {
>> + // SAFETY: per safety requirement.
>
> Same.
>
>> + unsafe { &mut *self.as_mut_ptr() }
>> + }
>> +
>> + /// Reads the value of `field` and ensures that its type is [`FromBytes`].
>> + ///
>> + /// # Safety
>> + ///
>> + /// This must be called from the [`dma_read`] macro which ensures that the `field` pointer is
>> + /// validated beforehand.
>> + ///
>> [...]
>> +
>> +impl<T: AsBytes + FromBytes> Coherent<T> {
>> + /// Allocates a region of `T` of coherent memory.
>> + #[expect(unused)]
>> + fn alloc_with_attrs(
>> dev: &device::Device<Bound>,
>> - count: usize,
>> gfp_flags: kernel::alloc::Flags,
>> dma_attrs: Attrs,
>> - ) -> Result<CoherentAllocation<T>> {
>> - build_assert!(
>> - core::mem::size_of::<T>() > 0,
>> - "It doesn't make sense for the allocated type to be a ZST"
>> - );
>> + ) -> Result<Self> {
>> + const {
>> + assert!(
>> + core::mem::size_of::<T>() > 0,
>> + "It doesn't make sense for the allocated type to be a ZST"
>> + );
>> + }
>>
>> - let size = count
>> - .checked_mul(core::mem::size_of::<T>())
>> - .ok_or(EOVERFLOW)?;
>> let mut dma_handle = 0;
>> // SAFETY: Device pointer is guaranteed as valid by the type invariant on `Device`.
>> let addr = unsafe {
>> bindings::dma_alloc_attrs(
>> dev.as_raw(),
>> - size,
>> + core::mem::size_of::<T>(),
>> &mut dma_handle,
>> gfp_flags.as_raw(),
>> dma_attrs.as_raw(),
>> )
>> };
>> - let addr = NonNull::new(addr).ok_or(ENOMEM)?;
>> + let cpu_addr = NonNull::new(addr.cast()).ok_or(ENOMEM)?;
>> // INVARIANT:
>> - // - We just successfully allocated a coherent region which is accessible for
>> - // `count` elements, hence the cpu address is valid. We also hold a refcounted reference
>> - // to the device.
>> - // - The allocated `size` is equal to `size_of::<T> * count`.
>> - // - The allocated `size` fits into a `usize`.
>> + // - We just successfully allocated a coherent region which is adequately sized for `T`,
>> + // hence the cpu address is valid.
>
> The invariant says "valid for the lifetime", do you need to argue for
> the duration of the validity?
It says "For the lifetime of an instance of ..." which is basically equal to
saying nothing. I think that part should just be removed.
>
>> + // - We also hold a refcounted reference to the device.
>
> This does not relate to the second invariant of `Self`.
The second invariant is about size, which is addressed in the first bullet
point. This is about the third invariant, which the doc-comemnt just says "TODO"
currently.
Best,
Gary
WARNING: multiple messages have this Message-ID (diff)
From: "Gary Guo" <gary@garyguo.net>
To: "Andreas Hindborg" <a.hindborg@kernel.org>,
"Danilo Krummrich" <dakr@kernel.org>, <aliceryhl@google.com>,
<acourbot@nvidia.com>, <ojeda@kernel.org>, <boqun@kernel.org>,
<gary@garyguo.net>, <bjorn3_gh@protonmail.com>,
<lossin@kernel.org>, <tmgross@umich.edu>,
<abdiel.janulgue@gmail.com>, <daniel.almeida@collabora.com>,
<robin.murphy@arm.com>
Cc: driver-core@lists.linux.dev, nouveau@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/8] rust: dma: add generalized container for types other than slices
Date: Tue, 24 Mar 2026 14:06:01 +0000 [thread overview]
Message-ID: <DHB2JCKXZ5ZN.LA5E3HY3YHGS@garyguo.net> (raw)
In-Reply-To: <877br1qr6v.fsf@kernel.org>
On Tue Mar 24, 2026 at 1:42 PM GMT, Andreas Hindborg wrote:
> "Danilo Krummrich" <dakr@kernel.org> writes:
>
>> + /// Returns a reference to the data in the region.
>> ///
>> - /// # Examples
>> + /// # Safety
>> ///
>> - /// ```
>> - /// # use kernel::device::{Bound, Device};
>> - /// use kernel::dma::{attrs::*, CoherentAllocation};
>> + /// * Callers must ensure that the device does not read/write to/from memory while the returned
>> + /// slice is live.
>> + /// * Callers must ensure that this call does not race with a write to the same region while
>> + /// the returned slice is live.
>> + #[inline]
>> + pub unsafe fn as_ref(&self) -> &T {
>> + // SAFETY: per safety requirement.
>
> Is this enough? Don't you need to assert a valid bit pattern? I assume
> you get this from `FromBytes`, but that bound is not on `T` in this impl
> block.
Concetually `Coherent<T>` is a container of `T` so it should always hold a valid
bit pattern for the type. Perhaps this should be added to the type invariant.
FromBytes is only needed at the constructor level as that's the only place where
you're asserting that initial bit pattern is valid.
>
>> + unsafe { &*self.as_ptr() }
>> + }
>> +
>> + /// Returns a mutable reference to the data in the region.
>> ///
>> - /// # fn test(dev: &Device<Bound>) -> Result {
>> - /// let c: CoherentAllocation<u64> =
>> - /// CoherentAllocation::alloc_attrs(dev, 4, GFP_KERNEL, DMA_ATTR_NO_WARN)?;
>> - /// # Ok::<(), Error>(()) }
>> - /// ```
>> - pub fn alloc_attrs(
>> + /// # Safety
>> + ///
>> + /// * Callers must ensure that the device does not read/write to/from memory while the returned
>> + /// slice is live.
>> + /// * Callers must ensure that this call does not race with a read or write to the same region
>> + /// while the returned slice is live.
>> + #[expect(clippy::mut_from_ref, reason = "unsafe to use API")]
>> + #[inline]
>> + pub unsafe fn as_mut(&self) -> &mut T {
>> + // SAFETY: per safety requirement.
>
> Same.
>
>> + unsafe { &mut *self.as_mut_ptr() }
>> + }
>> +
>> + /// Reads the value of `field` and ensures that its type is [`FromBytes`].
>> + ///
>> + /// # Safety
>> + ///
>> + /// This must be called from the [`dma_read`] macro which ensures that the `field` pointer is
>> + /// validated beforehand.
>> + ///
>> [...]
>> +
>> +impl<T: AsBytes + FromBytes> Coherent<T> {
>> + /// Allocates a region of `T` of coherent memory.
>> + #[expect(unused)]
>> + fn alloc_with_attrs(
>> dev: &device::Device<Bound>,
>> - count: usize,
>> gfp_flags: kernel::alloc::Flags,
>> dma_attrs: Attrs,
>> - ) -> Result<CoherentAllocation<T>> {
>> - build_assert!(
>> - core::mem::size_of::<T>() > 0,
>> - "It doesn't make sense for the allocated type to be a ZST"
>> - );
>> + ) -> Result<Self> {
>> + const {
>> + assert!(
>> + core::mem::size_of::<T>() > 0,
>> + "It doesn't make sense for the allocated type to be a ZST"
>> + );
>> + }
>>
>> - let size = count
>> - .checked_mul(core::mem::size_of::<T>())
>> - .ok_or(EOVERFLOW)?;
>> let mut dma_handle = 0;
>> // SAFETY: Device pointer is guaranteed as valid by the type invariant on `Device`.
>> let addr = unsafe {
>> bindings::dma_alloc_attrs(
>> dev.as_raw(),
>> - size,
>> + core::mem::size_of::<T>(),
>> &mut dma_handle,
>> gfp_flags.as_raw(),
>> dma_attrs.as_raw(),
>> )
>> };
>> - let addr = NonNull::new(addr).ok_or(ENOMEM)?;
>> + let cpu_addr = NonNull::new(addr.cast()).ok_or(ENOMEM)?;
>> // INVARIANT:
>> - // - We just successfully allocated a coherent region which is accessible for
>> - // `count` elements, hence the cpu address is valid. We also hold a refcounted reference
>> - // to the device.
>> - // - The allocated `size` is equal to `size_of::<T> * count`.
>> - // - The allocated `size` fits into a `usize`.
>> + // - We just successfully allocated a coherent region which is adequately sized for `T`,
>> + // hence the cpu address is valid.
>
> The invariant says "valid for the lifetime", do you need to argue for
> the duration of the validity?
It says "For the lifetime of an instance of ..." which is basically equal to
saying nothing. I think that part should just be removed.
>
>> + // - We also hold a refcounted reference to the device.
>
> This does not relate to the second invariant of `Self`.
The second invariant is about size, which is addressed in the first bullet
point. This is about the third invariant, which the doc-comemnt just says "TODO"
currently.
Best,
Gary
next prev parent reply other threads:[~2026-03-24 14:06 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 19:45 [PATCH v2 0/8] dma::Coherent & dma::CoherentBox API Danilo Krummrich
2026-03-20 19:45 ` [PATCH v2 1/8] rust: dma: use "kernel vertical" style for imports Danilo Krummrich
2026-03-24 14:02 ` Andreas Hindborg
2026-03-20 19:45 ` [PATCH v2 2/8] rust: dma: add generalized container for types other than slices Danilo Krummrich
2026-03-21 23:22 ` Aditya Rajan
2026-03-21 23:22 ` Aditya Rajan
2026-03-22 0:47 ` Gary Guo
2026-03-22 0:47 ` Gary Guo
2026-03-22 6:24 ` Aditya Rajan
2026-03-22 6:24 ` Aditya Rajan
2026-03-24 13:42 ` Andreas Hindborg
2026-03-24 14:06 ` Gary Guo [this message]
2026-03-24 14:06 ` Gary Guo
2026-03-24 14:37 ` Andreas Hindborg
2026-03-20 19:45 ` [PATCH v2 3/8] rust: dma: add zeroed constructor to `Coherent` Danilo Krummrich
2026-03-21 6:37 ` Alexandre Courbot
2026-03-21 6:37 ` Alexandre Courbot
2026-03-24 13:46 ` Andreas Hindborg
2026-03-20 19:45 ` [PATCH v2 4/8] rust: dma: introduce dma::CoherentBox for memory initialization Danilo Krummrich
2026-03-20 20:55 ` Gary Guo
2026-03-20 20:55 ` Gary Guo
2026-03-24 13:57 ` Andreas Hindborg
2026-03-20 19:45 ` [PATCH v2 5/8] rust: dma: add Coherent:init() and Coherent::init_with_attrs() Danilo Krummrich
2026-03-20 20:56 ` Gary Guo
2026-03-20 20:56 ` Gary Guo
2026-03-24 14:00 ` Andreas Hindborg
2026-03-24 15:03 ` Danilo Krummrich
2026-03-24 15:03 ` Danilo Krummrich
2026-03-24 15:40 ` Andreas Hindborg
2026-03-20 19:45 ` [PATCH v2 6/8] gpu: nova-core: use Coherent::init to initialize GspFwWprMeta Danilo Krummrich
2026-03-20 21:04 ` Gary Guo
2026-03-20 21:04 ` Gary Guo
2026-03-20 19:45 ` [PATCH v2 7/8] gpu: nova-core: convert Gsp::new() to use CoherentBox Danilo Krummrich
2026-03-20 21:06 ` Gary Guo
2026-03-20 21:06 ` Gary Guo
2026-03-20 19:45 ` [PATCH v2 8/8] gpu: nova-core: convert to new dma::Coherent API Danilo Krummrich
2026-03-21 16:50 ` Gary Guo
2026-03-21 16:50 ` Gary Guo
2026-03-21 18:22 ` Danilo Krummrich
2026-03-21 18:22 ` Danilo Krummrich
2026-03-21 22:36 ` Gary Guo
2026-03-21 22:36 ` Gary Guo
2026-03-21 5:13 ` [PATCH v2 0/8] dma::Coherent & dma::CoherentBox API Alexandre Courbot
2026-03-21 5:13 ` Alexandre Courbot
2026-03-23 21:56 ` Danilo Krummrich
2026-03-23 21:56 ` 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=DHB2JCKXZ5ZN.LA5E3HY3YHGS@garyguo.net \
--to=gary@garyguo.net \
--cc=a.hindborg@kernel.org \
--cc=abdiel.janulgue@gmail.com \
--cc=acourbot@nvidia.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=driver-core@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=nouveau@lists.freedesktop.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.