From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: gpu: nova-core: fb: make sure to unregister SysmemFlush on boot failure
Date: Sun, 12 Apr 2026 11:22:40 +1000 [thread overview]
Message-ID: <review-overall-20260409-fix-systemflush-v1-1-a1d6c968f17c@nvidia.com> (raw)
In-Reply-To: <20260409-fix-systemflush-v1-1-a1d6c968f17c@nvidia.com>
Overall Series Review
Subject: gpu: nova-core: fb: make sure to unregister SysmemFlush on boot failure
Author: Eliot Courtney <ecourtney@nvidia.com>
Patches: 3
Reviewed: 2026-04-12T11:22:40.453075
---
This is a single-patch fix for a real resource leak bug in `nova-core`. When `Gpu::new` fails after `SysmemFlush::register()` succeeds (e.g., during falcon creation or GSP boot), the sysmem flush page is leaked: it is freed by Rust's automatic drop of `CoherentHandle`, but the GPU hardware register still points to the now-freed DMA address. This could lead to the GPU writing to stale/reused memory.
The approach is sound: add a `Drop` impl that performs best-effort cleanup via revocable BAR access, while preserving the existing infallible manual `unregister()` path for normal teardown. The guard against double-unregister warnings (`registered_dma_handle != 0`) is a necessary and correct consequence of having both manual and automatic cleanup paths.
**Verdict: The patch is correct and should be accepted.** I have one minor observation below but no blocking issues.
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-04-12 1:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 12:15 [PATCH] gpu: nova-core: fb: make sure to unregister SysmemFlush on boot failure Eliot Courtney
2026-04-09 22:56 ` John Hubbard
2026-04-10 15:57 ` Gary Guo
2026-04-12 1:22 ` Claude Code Review Bot [this message]
2026-04-12 1:22 ` Claude review: " Claude Code Review 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=review-overall-20260409-fix-systemflush-v1-1-a1d6c968f17c@nvidia.com \
--to=claude-review@example.com \
--cc=dri-devel-reviews@example.com \
/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