public inbox for drm-ai-reviews@public-inbox.freedesktop.org
 help / color / mirror / Atom feed
From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/kmb: Fix error pointer dereference
Date: Mon, 23 Feb 2026 06:12:42 +1000	[thread overview]
Message-ID: <review-patch1-20260219224426.1122073-1-ethantidmore06@gmail.com> (raw)
In-Reply-To: <20260219224426.1122073-1-ethantidmore06@gmail.com>

Patch Review

The bug analysis in the commit message is accurate. Confirmed that `kmb_dsi_host_unregister()` immediately dereferences its argument:

```c
void kmb_dsi_host_unregister(struct kmb_dsi *kmb_dsi)
{
	kmb_dsi_clk_disable(kmb_dsi);
	mipi_dsi_host_unregister(kmb_dsi->host);
}
```

So passing an ERR_PTR here will crash.

There are two paths that reach `err_free1`:

1. `kmb_dsi_init()` fails -- `kmb->kmb_dsi` is an ERR_PTR, must not call unregister.
2. `kmb_hw_init()` fails -- `kmb->kmb_dsi` is a valid pointer, must call unregister.

The fix handles both correctly:

> +	if (!IS_ERR(kmb->kmb_dsi))
> +		kmb_dsi_host_unregister(kmb->kmb_dsi);

This works, though the more common kernel pattern for this situation is to add a separate goto label so the `kmb_dsi_init` failure path skips the unregister entirely, rather than adding a runtime check in the cleanup code. Something like having the `kmb_dsi_init` error path jump to a label after the unregister call (or before it, with `dev_set_drvdata` duplicated). The IS_ERR approach is functionally fine but slightly unusual for kernel error unwinding, where the convention is that each label corresponds to unwinding one specific resource.

That said, restructuring the labels would be a larger diff for minimal benefit. The fix as-is is correct and solves the bug.

No other issues found.

---
Generated by Claude Code Patch Reviewer

      parent reply	other threads:[~2026-02-22 20:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-19 22:44 [PATCH] drm/kmb: Fix error pointer dereference Ethan Tidmore
2026-02-22 20:12 ` Claude review: " Claude Code Review Bot
2026-02-22 20:12 ` Claude Code Review Bot [this message]

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-patch1-20260219224426.1122073-1-ethantidmore06@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