From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: gpu: host1x: Fix device reference leak in device_add() error path
Date: Mon, 13 Apr 2026 19:10:39 +1000 [thread overview]
Message-ID: <review-overall-20260412121836.2461556-1-lgs201920130244@gmail.com> (raw)
In-Reply-To: <20260412121836.2461556-1-lgs201920130244@gmail.com>
Overall Series Review
Subject: gpu: host1x: Fix device reference leak in device_add() error path
Author: Guangshuo Li <lgs201920130244@gmail.com>
Patches: 1
Reviewed: 2026-04-13T19:10:39.741073
---
This is a single-patch fix targeting a device reference leak in the `host1x_device_add()` error path when `device_add()` fails for a device with no subdevices. The identified bug is real: the original code logs the error but falls through to `return 0`, leaking the device reference and leaving a half-initialized device on `host1x->devices`.
However, **the proposed fix introduces a new bug** — a double list removal that will crash or warn on most kernel configurations. The `list_del()` call poisons the list pointers, and then `put_device()` triggers the release callback (`host1x_device_release` → `__host1x_device_del`) which calls `list_del_init()` on those same poisoned pointers. On kernels without `CONFIG_DEBUG_LIST` / `CONFIG_LIST_HARDENED` (i.e., most production kernels), this dereferences `LIST_POISON1`/`LIST_POISON2` and causes a kernel oops.
**Recommendation: Needs revision (NAK as-is).**
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-04-13 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-12 12:18 [PATCH] gpu: host1x: Fix device reference leak in device_add() error path Guangshuo Li
2026-04-13 9:10 ` Claude Code Review Bot [this message]
2026-04-13 9:10 ` 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-20260412121836.2461556-1-lgs201920130244@gmail.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