linux-kernel - Re: [PATCH v3 30/30] gpu: nova-core: clarify the GPU firmware boot steps

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <ebae8ac043bbcdf6b341185c480d43a6d7b4d337.camel@nvidia.com>
Date: Mon, 9 Feb 2026 04:24:47 +0000
From: Timur Tabi <ttabi@...dia.com>
To: Alexandre Courbot <acourbot@...dia.com>, "dakr@...nel.org"
	<dakr@...nel.org>, John Hubbard <jhubbard@...dia.com>
CC: "lossin@...nel.org" <lossin@...nel.org>, "a.hindborg@...nel.org"
	<a.hindborg@...nel.org>, "boqun.feng@...il.com" <boqun.feng@...il.com>, Zhi
 Wang <zhiw@...dia.com>, "simona@...ll.ch" <simona@...ll.ch>,
	"tmgross@...ch.edu" <tmgross@...ch.edu>, "alex.gaynor@...il.com"
	<alex.gaynor@...il.com>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "ojeda@...nel.org" <ojeda@...nel.org>,
	"nouveau@...ts.freedesktop.org" <nouveau@...ts.freedesktop.org>,
	"rust-for-linux@...r.kernel.org" <rust-for-linux@...r.kernel.org>,
	"bjorn3_gh@...tonmail.com" <bjorn3_gh@...tonmail.com>, Eliot Courtney
	<ecourtney@...dia.com>, Joel Fernandes <joelagnelf@...dia.com>,
	"airlied@...il.com" <airlied@...il.com>, "aliceryhl@...gle.com"
	<aliceryhl@...gle.com>, "bhelgaas@...gle.com" <bhelgaas@...gle.com>,
	"gary@...yguo.net" <gary@...yguo.net>, Alistair Popple <apopple@...dia.com>
Subject: Re: [PATCH v3 30/30] gpu: nova-core: clarify the GPU firmware boot
 steps

On Sun, 2026-02-08 at 18:22 -0800, John Hubbard wrote:
> > > Looks like you accidentally deleted the "if mbox0 != 0" test.
> > > 
> > 
> > OK, I've added it back in for the next version:
> > ...
> 
> ah, *correction*, I spoke too quickly. The reason I removed any
> such checks at some point is that they are wrong. This mailbox
> contains the libos address after boot, not an error code.
> 
> Open RM also does not check.

Hmmm.... I guess I'm reading the code wrong, but my understanding is that if mbox0 still
contains the libos address, then it means that the firmware didn't boot at all.

I will double-check.