From: Timur Tabi <ttabi@nvidia.com>
To: "dakr@kernel.org" <dakr@kernel.org>
Cc: "simona@ffwll.ch" <simona@ffwll.ch>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
"sunliming@linux.dev" <sunliming@linux.dev>,
"sunliming@kylinos.cn" <sunliming@kylinos.cn>,
"mripard@kernel.org" <mripard@kernel.org>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>
Subject: Re: [PATCH] drm/nouveau/gsp: Fix possible NULL pointer dereference warning in r535_dmac_alloc
Date: Sat, 18 Apr 2026 17:44:03 +0000 [thread overview]
Message-ID: <f3ea592561af59cf0d677e66a70165e2d7b7edbb.camel@nvidia.com> (raw)
In-Reply-To: <DHWGN6Y2J9X6.3FMWWDU2NQ2LV@kernel.org>
On Sat, 2026-04-18 at 19:35 +0200, Danilo Krummrich wrote:
> > I posted a patch a couple months ago that cleans up an IS_ERR check, but it was never picked
> > up:
>
> Thanks! Can you please make sure to send patches to all maintainers? If they
> don't land in my inbox, I can't pick them up. :(
M: Lyude Paul <lyude@redhat.com>
M: Danilo Krummrich <dakr@kernel.org>
Hmmmm.... I did CC Lyude, but you're right. I should update my git-email script to catch these
better.
While I have your attention, I do have other patches that I neglected to CC you on:
2. [PATCH 6/6] drm/nouveau/gsp: enable FWSEC-SB on GA100
- by Timur Tabi @ 2026-04-07 19:21 UTC [95%]
3. [PATCH 2/6] drm/nouveau/bios: specify correct display fuse register for Ampere and Ada
- by Timur Tabi @ 2026-04-07 19:21 UTC [95%]
4. [PATCH 1/6] drm/nouveau: check for GA100 specifically when calculating FRTS size
- by Timur Tabi @ 2026-04-07 19:21 UTC [91%]
5. [PATCH 4/6] drm/nouveau/gsp: require GSP-RM for GA100 support
- by Timur Tabi @ 2026-04-07 19:21 UTC [97%]
6. [PATCH 3/6] drm/nouveau/bios: skip the IFR header if present
- by Timur Tabi @ 2026-04-07 19:21 UTC [75%]
7. [PATCH 5/6] drm/nouveau: parse the VBIOS on GA100
- by Timur Tabi @ 2026-04-07 19:21 UTC [99%]
8. [PATCH 0/6] drm/nouveau: fix GA100 issues
- by Timur Tabi @ 2026-04-07 19:21 UTC [93%]
9. [PATCH] drm/nouveau: expose VBIOS via debugfs on GSP-RM systems
- by Timur Tabi @ 2026-04-07 18:53 UTC [95%]
>
> > https://lore.freedesktop.org/nouveau/20260103000756.1002890-1-ttabi@nvidia.com/T/#u
> >
> > I'm quite certain that there are other similar issues in Nouveau w.r.t. IS_ERR_OR_NULL.
>
> Yeah, that sounds likely.
>
> > I think an audit of the Nouveau error paths is in order. I suspect that Ben's big refactors
> > over the past year have resulted in some invalid error paths.
>
> Are you planning to look into this?
No, but it does sound like something that Claude could figure out pretty quick.
next prev parent reply other threads:[~2026-04-18 17:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-18 7:14 [PATCH] drm/nouveau/gsp: Fix possible NULL pointer dereference warning in r535_dmac_alloc sunliming
2026-04-18 12:12 ` Danilo Krummrich
2026-04-18 17:24 ` Timur Tabi
2026-04-18 17:35 ` Danilo Krummrich
2026-04-18 17:44 ` Timur Tabi [this message]
2026-04-18 20:43 ` Danilo Krummrich
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=f3ea592561af59cf0d677e66a70165e2d7b7edbb.camel@nvidia.com \
--to=ttabi@nvidia.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=simona@ffwll.ch \
--cc=sunliming@kylinos.cn \
--cc=sunliming@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