From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/amdgpu: clamp user gartsize against device capacity
Date: Sat, 16 May 2026 10:27:15 +1000 [thread overview]
Message-ID: <review-overall-20260514194937.35649-1-en22ue@gmail.com> (raw)
In-Reply-To: <20260514194937.35649-1-en22ue@gmail.com>
Overall Series Review
Subject: drm/amdgpu: clamp user gartsize against device capacity
Author: Ahmed Elmetwally <en22ue@gmail.com>
Patches: 1
Reviewed: 2026-05-16T10:27:15.093189
---
**This patch is based on a stale tree and will not apply.** The upstream code has already been refactored: the inline gart size logic in each `gmc_v*_0.c` backend was consolidated into a shared `amdgpu_gmc_set_gart_size()` helper (see `amdgpu_gmc.c:283`). The patch's diff context in `gmc_v11_0.c` expects the old inline code (`if (amdgpu_gart_size == -1) ... else ...`) which no longer exists — the current tree has a single call to `amdgpu_gmc_set_gart_size(adev, SZ_512M)` at line 712.
The underlying problem (an absurdly large `amdgpu.gartsize` parameter causing probe failure) is real and the commit message is well-written with a clear reproducer. However, the correct fix should modify the existing `amdgpu_gmc_set_gart_size()` function rather than introducing a parallel `amdgpu_gmc_validate_gart_size()` helper. This would fix all gmc backends (v6 through v12) in one shot rather than requiring per-backend follow-up patches.
Additionally, the patch has several technical issues detailed below.
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-16 0:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 19:49 [PATCH] drm/amdgpu: clamp user gartsize against device capacity Ahmed Elmetwally
2026-05-16 0:27 ` Claude Code Review Bot [this message]
2026-05-16 0:27 ` 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-20260514194937.35649-1-en22ue@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