linux-kernel - Re: [PATCH 29/31] gpu: nova-core: Hopper/Blackwell: add FSP Chain of Trust boot path

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <08e6bc5a-cc41-44e4-9c7e-9e11f8aaf962@nvidia.com>
Date: Mon, 26 Jan 2026 11:53:53 -0800
From: John Hubbard <jhubbard@...dia.com>
To: Gary Guo <gary@...yguo.net>, Danilo Krummrich <dakr@...nel.org>
Cc: Alexandre Courbot <acourbot@...dia.com>,
 Joel Fernandes <joelagnelf@...dia.com>, Timur Tabi <ttabi@...dia.com>,
 Alistair Popple <apopple@...dia.com>, Edwin Peer <epeer@...dia.com>,
 Zhi Wang <zhiw@...dia.com>, David Airlie <airlied@...il.com>,
 Simona Vetter <simona@...ll.ch>, Bjorn Helgaas <bhelgaas@...gle.com>,
 Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>,
 Boqun Feng <boqun.feng@...il.com>, Björn Roy Baron
 <bjorn3_gh@...tonmail.com>, Benno Lossin <lossin@...nel.org>,
 Andreas Hindborg <a.hindborg@...nel.org>, Alice Ryhl <aliceryhl@...gle.com>,
 Trevor Gross <tmgross@...ch.edu>, nouveau@...ts.freedesktop.org,
 rust-for-linux@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 29/31] gpu: nova-core: Hopper/Blackwell: add FSP Chain of
 Trust boot path

On 1/26/26 5:08 AM, Gary Guo wrote:
> On Sat Jan 24, 2026 at 1:42 AM GMT, John Hubbard wrote:
>> On 1/23/26 5:38 PM, John Hubbard wrote:
>>> On 1/21/26 8:35 AM, Gary Guo wrote:
>>>> On Wed Dec 3, 2025 at 5:59 AM GMT, John Hubbard wrote:
...
>>      // SAFETY: fmc_full, which contains the complete FMC ELF file, is never submitted to
>>      // hardware, so it is safe from hardware-software races. And we are the unique owner of
>>      // fsp_fw (and therefore of fsp_fw.fmc_full). (A separate buffer, fsp_fw.fmc_image, is what
>>      // gets submitted to the hardware).
>>      let fmc_full_data = unsafe { fsp_fw.fmc_full.as_slice(0, fsp_fw.fmc_full.size())? };
> 
> If they're never submitted to hardware, why are they dma objects?
> 

ah, right. That's leftover from my earlier bringup work. Of course,
these can be separate allocations. If I change fmc_full to KVec<u8>,
then the whole unsafe block just disappears.

I've fixed this for v2, thanks for spotting that.

thanks,
-- 
John Hubbard