From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/amdgpu: fix sleeping allocation under spinlock in PASID IDR
Date: Tue, 31 Mar 2026 17:50:57 +1000 [thread overview]
Message-ID: <review-patch1-20260328213900.19255-1-mikhail.v.gavrilov@gmail.com> (raw)
In-Reply-To: <20260328213900.19255-1-mikhail.v.gavrilov@gmail.com>
Patch Review
**Analysis of the bug:** Confirmed by reading the current tree at `amdgpu_ids.c:70-73` — the code currently calls `idr_alloc_cyclic()` with `GFP_KERNEL` while holding `amdgpu_pasid_idr_lock` (a spinlock). This is indeed a sleeping-in-atomic-context bug.
**Analysis of the fix:**
```c
+ idr_preload(GFP_KERNEL);
spin_lock(&amdgpu_pasid_idr_lock);
pasid = idr_alloc_cyclic(&amdgpu_pasid_idr, NULL, 1,
- 1U << bits, GFP_KERNEL);
+ 1U << bits, GFP_NOWAIT);
spin_unlock(&amdgpu_pasid_idr_lock);
+ idr_preload_end();
```
This is textbook correct:
1. `idr_preload(GFP_KERNEL)` pre-allocates radix tree nodes (can sleep, called outside spinlock) and disables preemption.
2. `GFP_NOWAIT` inside the spinlock ensures the allocator uses the preloaded pool and never sleeps.
3. `idr_preload_end()` re-enables preemption after the spinlock is released.
**One minor ordering note:** `idr_preload_end()` is called after `spin_unlock()`, which is correct — `idr_preload()` disables preemption, so you must hold the preload context across the allocation. The unlock-before-preload_end ordering is the standard pattern (see e.g., `drivers/infiniband/`, `net/core/`).
**Fixes tag and Cc: stable** are both appropriate since this is a straightforward bugfix for a commit that introduced the regression.
**No issues found.**
Reviewed-by recommendation: This patch is correct and follows established kernel patterns.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-03-31 7:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-28 21:39 [PATCH] drm/amdgpu: fix sleeping allocation under spinlock in PASID IDR Mikhail Gavrilov
2026-03-30 7:31 ` Lazar, Lijo
2026-03-31 7:50 ` Claude Code Review Bot [this message]
2026-03-31 7:50 ` Claude review: " Claude Code Review Bot
-- strict thread matches above, loose matches on Subject: below --
2026-03-30 5:30 [PATCH v2 0/2] drm/amdgpu: fix locking issues in PASID IDR management Mikhail Gavrilov
2026-03-30 5:30 ` [PATCH v2 1/2] drm/amdgpu: fix sleeping allocation under spinlock in PASID IDR Mikhail Gavrilov
2026-03-31 7:36 ` 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-patch1-20260328213900.19255-1-mikhail.v.gavrilov@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