All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Pedro Yudi Honda" <niyudi.honda@usp.br>
Cc: "Danilo Krummrich" <dakr@kernel.org>,
	"Alexandre Courbot" <acourbot@nvidia.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/7] drm/nova: use `zerocopy` in vbios.rs
Date: Thu, 25 Jun 2026 19:16:38 +0000	[thread overview]
Message-ID: <20260625191638.B8B591F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260625190553.7245-3-niyudi.honda@usp.br>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:

Pre-existing issues:
- [High] VBIOS byte stream reconstruction from MMIO uses `to_ne_bytes()` and struct parsing uses native integer types, corrupting VBIOS reading on big-endian architectures.
--

commit 1cc33aae3ba2ca65527c5d72b5ee976f3c73ac92
Author: Pedro Yudi Honda <niyudi.honda@usp.br>

drm/nova: use `zerocopy` in vbios.rs
    
This commit replaces the `transmute::FromBytes` trait with its `zerocopy`
equivalent for various VBIOS structures in vbios.rs. It also updates the
call sites accordingly to use the new trait methods.

> diff --git a/drivers/gpu/nova-core/vbios.rs b/drivers/gpu/nova-core/vbios.rs
> index e6d144587c4ee..a3c0c06f6818d 100644
> --- a/drivers/gpu/nova-core/vbios.rs
> +++ b/drivers/gpu/nova-core/vbios.rs

[ ... ]

> @@ -359,7 +356,7 @@ pub(crate) fn fwsec_image(&self) -> &FwSecBiosImage {
>  }
>  
>  /// PCI Data Structure as defined in PCI Firmware Specification
> -#[derive(Debug, Clone)]
> +#[derive(Debug, Clone, FromBytes)]
>  #[repr(C)]
>  struct PcirStruct {
>      /// PCI Data Structure signature ("PCIR" or "NPDS")
>      signature: [u8; 4],
>      /// PCI Vendor ID (e.g., 0x10DE for NVIDIA)
>      vendor_id: u16,

[Severity: High]
This is a pre-existing issue, but since the VBIOS structures map directly to
little-endian VBIOS data, does using native integer types like u16 cause
the parsing to fail on big-endian architectures?

Also, since VbiosIterator::read_more() converts MMIO 32-bit words back into a
byte stream using word.to_ne_bytes():

    word.to_ne_bytes()
        .iter()
        .try_for_each(|&b| self.data.push(b, GFP_KERNEL))?;

doesn't this byte-swap the little-endian hardware register data on big-endian
systems?

Should explicit little-endian types (e.g.,
zerocopy::byteorder::little_endian::U16) and word.to_le_bytes() be used to
ensure the correct byte order is maintained?

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260625190553.7245-1-niyudi.honda@usp.br?part=2

  reply	other threads:[~2026-06-25 19:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-25 19:05 [PATCH 0/7] drm/nova: replace `transmute` with `zerocopy` Pedro Yudi Honda
2026-06-25 19:05 ` [PATCH 1/7] drm/nova: use `zerocopy` in firmware.rs Pedro Yudi Honda
2026-06-25 19:05 ` [PATCH 2/7] drm/nova: use `zerocopy` in vbios.rs Pedro Yudi Honda
2026-06-25 19:16   ` sashiko-bot [this message]
2026-06-25 19:05 ` [PATCH 3/7] drm/nova: use `zerocopy` in booter.rs Pedro Yudi Honda
2026-06-25 19:14   ` sashiko-bot
2026-06-25 19:05 ` [PATCH 4/7] drm/nova: use `zerocopy` in fwsec.rs Pedro Yudi Honda
2026-06-25 19:05 ` [PATCH 5/7] drm/nova: use `zerocopy` in bootloader.rs Pedro Yudi Honda
2026-06-25 19:05 ` [PATCH 6/7] drm/nova: use `zerocopy` in riscv.rs Pedro Yudi Honda
2026-06-25 19:05 ` [PATCH 7/7] drm/nova: remove unused trait in commands.rs Pedro Yudi Honda
2026-06-25 19:11   ` sashiko-bot
2026-06-25 21:38 ` [PATCH 0/7] drm/nova: replace `transmute` with `zerocopy` Danilo Krummrich
2026-06-26 13:15   ` Nicolás Antinori
  -- strict thread matches above, loose matches on Subject: below --
2026-06-25 20:51 [RESEND PATCH " Pedro Yudi Honda
2026-06-25 20:51 ` [PATCH 2/7] drm/nova: use `zerocopy` in vbios.rs Pedro Yudi Honda
2026-06-25 21:14   ` 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=20260625191638.B8B591F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=dakr@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=niyudi.honda@usp.br \
    --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 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.