From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/msm/a6xx: Add missing aperture_lock init
Date: Wed, 25 Mar 2026 07:43:57 +1000 [thread overview]
Message-ID: <review-patch1-20260323161603.1165108-1-robin.clark@oss.qualcomm.com> (raw)
In-Reply-To: <20260323161603.1165108-1-robin.clark@oss.qualcomm.com>
Patch Review
**Correctness:** The fix is correct. The `aperture_lock` spinlock field in `struct a6xx_gpu` (declared at `a6xx_gpu.h:112`) is used in `a8xx_gpu.c` at lines 40, 50, 77, and 80 via `spin_lock_irqsave()`/`spin_unlock_irqrestore()`, but was never initialized. Using an uninitialized spinlock is undefined behavior and can lead to lockups or data corruption, especially with `CONFIG_DEBUG_SPINLOCK` enabled.
**Placement:** The init is correctly placed in `a6xx_gpu_init()` right next to the existing `mutex_init(&a6xx_gpu->gmu.lock)` at line 2658, which is the natural location for lock initialization in this function.
```
mutex_init(&a6xx_gpu->gmu.lock);
+ spin_lock_init(&a6xx_gpu->aperture_lock);
```
**Fixes tag:** The `Fixes: 288a93200892 ("drm/msm/adreno: Introduce A8x GPU Support")` tag correctly identifies the commit that introduced the field and its usage without the corresponding initialization.
**No issues found.** This is a clean, minimal fix.
Reviewed-by worthy.
---
Generated by Claude Code Patch Reviewer
prev parent reply other threads:[~2026-03-24 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 16:16 [PATCH] drm/msm/a6xx: Add missing aperture_lock init Rob Clark
2026-03-23 17:42 ` Dmitry Baryshkov
2026-03-23 17:55 ` Akhil P Oommen
2026-03-24 9:23 ` Konrad Dybcio
2026-03-24 21:43 ` Claude review: " Claude Code Review Bot
2026-03-24 21:43 ` 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-20260323161603.1165108-1-robin.clark@oss.qualcomm.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