Linux PCI subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Gary Guo" <gary@garyguo.net>
Cc: ojeda@kernel.org, "Alexandre Courbot" <acourbot@nvidia.com>,
	linux-pci@vger.kernel.org, "Danilo Krummrich" <dakr@kernel.org>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v6 03/20] rust: io: restrict untyped IO access and `register!` to `Region`
Date: Mon, 06 Jul 2026 13:03:54 +0000	[thread overview]
Message-ID: <20260706130354.B39F81F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260706-io_projection-v6-3-72cd5d055d54@garyguo.net>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Infallible 64-bit I/O accesses (`read64`, `write64`, etc.) will fail to compile on 64-bit systems due to a failing `const_assert!` in `io_view_assert` (formerly `io_addr_assert`).
--

commit 9e28956aa7e8253fe2ab41dc7ddbf9af5d160ab2
Author: Gary Guo <gary@garyguo.net>

rust: io: restrict untyped IO access and register! to Region

This commit restricts untyped I/O accesses and the register macro to the Region
type. It adds a generic type to IoLoc to indicate allowed base types, paving
the way for typed register blocks.

Link: https://lore.kernel.org/rust-for-linux/DHLB3RO3OSF5.2R7F27U99BKLN@nvidia.com/

> diff --git a/rust/kernel/io.rs b/rust/kernel/io.rs
> index d821ee48ed317..87141eb070564 100644
> --- a/rust/kernel/io.rs
> +++ b/rust/kernel/io.rs

[ ... ]

> @@ -437,6 +449,7 @@ fn read32(&self, offset: usize) -> u32
>      #[inline(always)]
>      fn read64(&self, offset: usize) -> u64
>      where
> +        usize: IoLoc<Self::Target, u64, IoType = u64>,
>          Self: IoCapable<u64>,
>      {
>          self.read(offset)

[Severity: High]
Does this regression cause a failure to compile when a driver invokes an
infallible 64-bit access method on 64-bit systems?

By restricting usize offsets to target Region, invoking an infallible 64-bit
access like read64(), write64(), or write_reg() with 64-bit registers
instantiates io_addr_assert() with U = u64.

Region has a hardcoded MIN_ALIGN of 4. The compile-time check explicitly
requires:

const_assert!(Alignment::of::<U>().as_usize() <= Self::Target::MIN_ALIGN.as_usize());

On 64-bit architectures, align_of::<u64>() is 8. Thus, 8 <= 4 evaluates to
false, causing an immediate unconditional compilation error for any driver
attempting to perform an infallible 64-bit MMIO access. Fallible variants
like try_read64() use runtime alignment checks and are unaffected.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260706-io_projection-v6-0-72cd5d055d54@garyguo.net?part=3

  reply	other threads:[~2026-07-06 13:03 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06 12:44 [PATCH v6 00/20] rust: I/O type generalization and projection Gary Guo
2026-07-06 12:44 ` [PATCH v6 01/20] rust: io: add dynamically-sized `Region` type Gary Guo
2026-07-06 12:54   ` sashiko-bot
2026-07-06 12:44 ` [PATCH v6 02/20] rust: io: add missing safety requirement in `IoCapable` methods Gary Guo
2026-07-06 13:00   ` sashiko-bot
2026-07-06 12:44 ` [PATCH v6 03/20] rust: io: restrict untyped IO access and `register!` to `Region` Gary Guo
2026-07-06 13:03   ` sashiko-bot [this message]
2026-07-06 12:44 ` [PATCH v6 04/20] rust: io: implement `Io` on reference types instead Gary Guo
2026-07-06 12:53   ` sashiko-bot
2026-07-06 12:44 ` [PATCH v6 05/20] rust: io: generalize `MmioRaw` to pointer to arbitrary type Gary Guo
2026-07-06 12:56   ` sashiko-bot
2026-07-06 12:44 ` [PATCH v6 06/20] rust: io: rename `Mmio` to `MmioOwned` Gary Guo
2026-07-06 12:57   ` sashiko-bot
2026-07-06 12:44 ` [PATCH v6 07/20] rust: io: implement `Mmio` as view type Gary Guo
2026-07-06 12:59   ` sashiko-bot
2026-07-06 12:44 ` [PATCH v6 08/20] rust: pci: io: make `ConfigSpace` a view Gary Guo
2026-07-06 12:51   ` sashiko-bot
2026-07-06 12:44 ` [PATCH v6 09/20] rust: io: use view types instead of addresses for `Io` Gary Guo
2026-07-06 12:57   ` sashiko-bot
2026-07-06 12:44 ` [PATCH v6 10/20] pwm: th1520: remove unnecessary `deref` Gary Guo
2026-07-06 12:48   ` sashiko-bot
2026-07-06 12:44 ` [PATCH v6 11/20] rust: io: remove `MmioOwned` Gary Guo
2026-07-06 12:54   ` sashiko-bot
2026-07-06 12:44 ` [PATCH v6 12/20] rust: io: move `Io` methods to extension trait Gary Guo
2026-07-06 12:51   ` sashiko-bot
2026-07-06 12:44 ` [PATCH v6 13/20] rust: io: add projection macro and methods Gary Guo
2026-07-06 12:58   ` sashiko-bot
2026-07-06 12:44 ` [PATCH v6 14/20] rust: io: add I/O backend for system memory with volatile access Gary Guo
2026-07-06 13:01   ` sashiko-bot
2026-07-06 12:44 ` [PATCH v6 15/20] rust: io: implement a view type for `Coherent` Gary Guo
2026-07-06 13:03   ` sashiko-bot
2026-07-06 12:44 ` [PATCH v6 16/20] rust: io: add `read_val` and `write_val` functions on `Io` Gary Guo
2026-07-06 12:59   ` sashiko-bot
2026-07-06 12:44 ` [PATCH v6 17/20] gpu: nova-core: use I/O projection for cleaner encapsulation Gary Guo
2026-07-06 13:07   ` sashiko-bot
2026-07-06 12:44 ` [PATCH v6 18/20] rust: dma: drop `dma_read!` and `dma_write!` API Gary Guo
2026-07-06 13:10   ` sashiko-bot
2026-07-06 12:44 ` [PATCH v6 19/20] rust: io: add copying methods Gary Guo
2026-07-06 13:09   ` sashiko-bot
2026-07-06 12:44 ` [PATCH v6 20/20] rust: io: implement `IoSysMap` Gary Guo
2026-07-06 12:59   ` sashiko-bot

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=20260706130354.B39F81F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gary@garyguo.net \
    --cc=linux-pci@vger.kernel.org \
    --cc=ojeda@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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