From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/loongson: clean up KMS polling on probe failure
Date: Sat, 16 May 2026 14:50:22 +1000 [thread overview]
Message-ID: <review-overall-20260511170152.16957-1-mhun512@gmail.com> (raw)
In-Reply-To: <20260511170152.16957-1-mhun512@gmail.com>
Overall Series Review
Subject: drm/loongson: clean up KMS polling on probe failure
Author: Myeonghun Pak <mhun512@gmail.com>
Patches: 4
Reviewed: 2026-05-16T14:50:22.210155
---
This is a single patch that addresses a real bug: `drm_kms_helper_poll_init()` is called during probe but `drm_kms_helper_poll_fini()` is never called on either the error paths or the remove path. The analysis is correct — the polling timer/work would leak on probe failure and on device removal.
However, **the proposed fix is not the right approach**. The loongson driver already uses `devm_drm_dev_alloc()` and `drmm_mode_config_init()` — it follows the DRM managed resource pattern. The proper fix is to replace `drm_kms_helper_poll_init()` with `drmm_kms_helper_poll_init()` (a one-line change), which registers a managed cleanup action so that `drm_kms_helper_poll_fini()` is called automatically when the DRM device is torn down. This eliminates the need for any manual `goto` cleanup labels or explicit `poll_fini` calls in remove.
Additionally, the remove-path change has an ordering concern: the patch places `drm_kms_helper_poll_fini()` **before** `drm_dev_unregister()`, but the standard tear-down order (as seen in e.g. `verisilicon/vs_drm.c`) is to unregister first, then finalize polling. Calling `poll_fini` while the device is still registered could race with connector probing triggered by userspace.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-16 4:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 17:01 [PATCH] drm/loongson: clean up KMS polling on probe failure Myeonghun Pak
2026-05-11 17:22 ` Icenowy Zheng
2026-05-12 6:26 ` Thomas Zimmermann
2026-05-12 6:35 ` Myeonghun Pak
2026-05-16 4:50 ` Claude Code Review Bot [this message]
2026-05-16 4:50 ` 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-20260511170152.16957-1-mhun512@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