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/mipi-dsi: fix of_node reference leak in of_mipi_dsi_device_add error path
Date: Mon, 25 May 2026 16:47:47 +1000	[thread overview]
Message-ID: <review-patch1-20260525045028.3895931-1-vulab@iscas.ac.cn> (raw)
In-Reply-To: <20260525045028.3895931-1-vulab@iscas.ac.cn>

Patch Review

**Correctness: Good.** The bug analysis is accurate. `of_node_get(node)` at line 182 takes a reference, and none of the failure paths inside `mipi_dsi_device_register_full()` release it. The fix correctly calls `of_node_put(node)` (not `of_node_put(info.node)` — both point to the same node, but using `node` directly is fine since `info.node` was set to `of_node_get(node)`).

**Minor style nit:** The new variable declaration breaks reverse-Christmas-tree ordering:

```c
struct mipi_dsi_device_info info = { };
int ret;
struct mipi_dsi_device *dsi;
u32 reg;
```

Per kernel coding conventions, local variable declarations should go longest-to-shortest line. The preferred ordering would be:

```c
struct mipi_dsi_device_info info = { };
struct mipi_dsi_device *dsi;
u32 reg;
int ret;
```

This is a trivial style issue and shouldn't block the patch, but a v2 could clean it up.

**Commit message:** Well-written. The explanation of why `device_set_node()` doesn't take its own reference is helpful context. The `Fixes:` tag and `Cc: stable` are appropriate.

**One observation for the commit message:** The message says "when `mipi_dsi_device_register_full()` fails (e.g., `mipi_dsi_device_add()` returns an error)" — it's worth noting that the early validation checks in `mipi_dsi_device_register_full()` (invalid channel, NULL info) also leak the reference, not just the `mipi_dsi_device_add()` sub-failure. The fix handles all of these, which is correct.

**Recommendation:** Acked with the suggestion to fix the declaration ordering in a v2 if the maintainer prefers it.

---
Generated by Claude Code Patch Reviewer

      parent reply	other threads:[~2026-05-25  6:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-25  4:50 [PATCH] drm/mipi-dsi: fix of_node reference leak in of_mipi_dsi_device_add error path Wentao Liang
2026-05-25  6:47 ` Claude review: " Claude Code Review Bot
2026-05-25  6:47 ` 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-20260525045028.3895931-1-vulab@iscas.ac.cn \
    --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