From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/amdgpu: fix lock leak on ENOMEM in AMDGPU_GEM_OP_GET_MAPPING_INFO
Date: Mon, 18 May 2026 16:08:13 +1000 [thread overview]
Message-ID: <review-overall-20260517131742.3435209-1-michael.bommarito@gmail.com> (raw)
In-Reply-To: <20260517131742.3435209-1-michael.bommarito@gmail.com>
Overall Series Review
Subject: drm/amdgpu: fix lock leak on ENOMEM in AMDGPU_GEM_OP_GET_MAPPING_INFO
Author: Michael Bommarito <michael.bommarito@gmail.com>
Patches: 1
Reviewed: 2026-05-18T16:08:13.978576
---
This is a single-patch series fixing a genuine resource leak bug in `amdgpu_gem_op_ioctl()`. The analysis is correct: when `kvcalloc()` fails at line 1093, the original code returned `-ENOMEM` directly, bypassing the `out_exec` cleanup label. This leaked the `drm_exec` lock context (which holds the GEM object's `dma_resv` and the VM root PD's `dma_resv`) and the `drm_gem_object` reference.
The fix is mechanical and obviously correct — it sets `r = -ENOMEM` and jumps to `out_exec`, which calls `drm_exec_fini(&exec)` and `drm_gem_object_put(gobj)`, matching the cleanup pattern used by every other error path in this function.
The commit message is thorough and well-written. It identifies the specific resources leaked, explains the user-visible impact (unprivileged local DoS via stuck D-state task), references the related work by Ziyi Guo on `num_entries` validation, and correctly notes the fix was not runtime-tested on patched kernel. The `Fixes:` and `Cc: stable` tags are appropriate.
**Verdict: This patch looks correct and ready to apply.**
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-18 6:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-17 13:17 [PATCH] drm/amdgpu: fix lock leak on ENOMEM in AMDGPU_GEM_OP_GET_MAPPING_INFO Michael Bommarito
2026-05-18 6:08 ` Claude Code Review Bot [this message]
2026-05-18 6:08 ` 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-20260517131742.3435209-1-michael.bommarito@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