From: Daniel Campos Ramos <Capitain_Jack@yahoo.com>
To: jim.cromie@gmail.com
Cc: Lyude Paul <lyude@redhat.com>, Danilo Krummrich <dakr@kernel.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Dave Airlie <airlied@redhat.com>,
dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] nouveau: fix 3 null-ptr derefs
Date: Sat, 3 Oct 2026 18:20:10 -0300 [thread overview]
Message-ID: <20261003212010.113714-1-Capitain_Jack@yahoo.com> (raw)
In-Reply-To: <20261002-my-fixups-v1-0-a83d20f9d3fe@gmail.com>
Hi Jim,
I tested patches 1/3 and 2/3 on 7.3.0-rc1, with an RTX 3060 (GA106)
passed through to a VM (vfio-pci). Patch 3/3 does not apply on 7.3-rc1
(nvkm_gsp_gcx_ready() is not there yet), so it is untested here.
Without firmware (the whole nvidia/ga106 folder removed and the
initramfs rebuilt), nouveau reports acr, gr and sec2 "firmware
unavailable", so there is no GR engine:
- GETPARAM with NOUVEAU_GETPARAM_GRAPH_UNITS returns -ENODEV and logs
"GETPARAM_GRAPH_UNITS: no gr engine or func"; the desktop session
already reached that path at boot.
- DRM_IOCTL_NOUVEAU_GET_ZCULL_INFO returns -ENOTTY.
I also called both ioctls directly from a small test program on the
render node. No oops anywhere: KWin composites, NVK declines the device
and zink falls back to llvmpipe.
With the firmware restored, GSP-RM 570.144 loads, there is no oops, and
the card drives a Sony 3D TV in every HDMI 1.4 3D structure it declares,
at 12 bpc.
On your worry about firmware: the most "damaging" thing in all of this
testing was the TV getting stuck on a corrupted signal during an earlier
no-firmware run, solved by power-cycling it and feeding it a proper
signal. No GPU firmware is ever written, and the firmware files in the
VM are disposable.
The kernel logs, the test program and its output are here:
https://github.com/danielcamposramos/sony-bravia-linux/tree/main/docs/upstream/nouveau-null-v3-test-2026-10-03
Tested-by: Daniel Campos Ramos <Capitain_Jack@yahoo.com> # 1/3 and 2/3, GA106
The test was run with an AI assistant doing the legwork under my
direction; the results above are what I saw on the hardware.
Daniel
next prev parent reply other threads:[~2026-10-03 21:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 18:09 Jim Cromie via B4 Relay
2026-10-02 18:09 ` [PATCH 1/3] drm/nouveau: Fix NULL pointer dereferences in GETPARAM ioctl Jim Cromie via B4 Relay
2026-10-08 22:18 ` lyude
2026-10-02 18:09 ` [PATCH 2/3] drm/nouveau: Fix NULL pointer dereference in GET_ZCULL_INFO ioctl Jim Cromie via B4 Relay
2026-10-08 22:19 ` lyude
2026-10-02 18:09 ` [PATCH 3/3] drm/nouveau/gsp: Fix NULL dereference in nvkm_gsp_gcx_ready() Jim Cromie via B4 Relay
2026-10-08 22:19 ` lyude
2026-10-03 21:20 ` Daniel Campos Ramos [this message]
2026-10-03 23:26 ` [PATCH 0/3] nouveau: fix 3 null-ptr derefs Lyude Paul
2026-10-08 3:04 ` jim.cromie
2026-10-08 19:24 ` lyude
2026-10-08 22:32 ` lyude
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=20261003212010.113714-1-Capitain_Jack@yahoo.com \
--to=capitain_jack@yahoo.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jim.cromie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®