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: Add splash DRM client
Date: Sat, 16 May 2026 16:02:57 +1000	[thread overview]
Message-ID: <review-overall-20260510-drm_client_splash-v3-0-a9aee9f0b2fc@valla.it> (raw)
In-Reply-To: <20260510-drm_client_splash-v3-0-a9aee9f0b2fc@valla.it>

Overall Series Review

Subject: Add splash DRM client
Author: Francesco Valla <francesco@valla.it>
Patches: 6
Reviewed: 2026-05-16T16:02:57.224131

---

This is a v3 RFC series adding a DRM-based splash screen client (3 patches). The concept is sound and addresses a long-standing TODO item. The implementation follows existing DRM client patterns (modeled after `drm_log.c`) and supports three image sources: plain color background, BMP firmware, and EFI BGRT. The Kconfig structure is reasonable and the code is generally well-structured.

However, there are several issues ranging from potential crashes to data integrity bugs that should be addressed before this moves past RFC stage.

**Key concerns:**
1. **Uninitialized thread pointer crash** in unregister path when hotplug never fires.
2. **Out-of-bounds memory read** in BMP pixel blitting (reading 4 bytes from 3-byte pixel data).
3. **Render thread sleep/wake race condition** — the classic `set_current_state` vs `wake_up_process` pattern has a window for lost wakeups.
4. **Tiled display dimension accumulation** looks swapped (hdisplay vs vdisplay).
5. **`modeset_mask` / scanout indexing** is broken — `j` doesn't track scanout indices correctly.

---

---
Generated by Claude Code Patch Reviewer

      parent reply	other threads:[~2026-05-16  6:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-10 21:29 [PATCH RFC v3 0/3] Add splash DRM client Francesco Valla
2026-05-10 21:29 ` [PATCH RFC v3 1/3] drm: client: add splash client Francesco Valla
2026-05-16  6:02   ` Claude review: " Claude Code Review Bot
2026-05-10 21:29 ` [PATCH RFC v3 2/3] MAINTAINERS: add entry for DRM " Francesco Valla
2026-05-16  6:02   ` Claude review: " Claude Code Review Bot
2026-05-10 21:29 ` [PATCH RFC v3 3/3] drm: docs: remove bootsplash from TODO Francesco Valla
2026-05-16  6:02   ` Claude review: " Claude Code Review Bot
2026-05-12  1:59 ` [PATCH RFC v3 0/3] Add splash DRM client Mario Limonciello
2026-05-12 17:41   ` Francesco Valla
2026-05-16  6:02 ` 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-overall-20260510-drm_client_splash-v3-0-a9aee9f0b2fc@valla.it \
    --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