From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: rust: drm: gem: shmem: Add DmaResvGuard helper
Date: Thu, 04 Jun 2026 11:29:38 +1000 [thread overview]
Message-ID: <review-patch2-20260603195210.693856-3-lyude@redhat.com> (raw)
In-Reply-To: <20260603195210.693856-3-lyude@redhat.com>
Patch Review
**Verdict: Minor concerns.**
The RAII guard pattern is correct. However:
**Return value of `dma_resv_lock()` is discarded:**
```rust
fn new(obj: &'a Object<T, C>) -> Self {
// SAFETY: This lock is initialized throughout the lifetime of `object`.
unsafe { bindings::dma_resv_lock(obj.raw_dma_resv(), ptr::null_mut()) };
Self(obj)
}
```
`dma_resv_lock()` returns `int` (it wraps `ww_mutex_lock()`). With `ctx = NULL`, it degrades to a plain mutex lock that always returns 0, so this is safe in practice -- and matches the C-side pattern in `drm_gem_shmem_release()` which also discards the return. But the safety comment should mention *why* the return value is ignored (i.e., NULL ctx guarantees success). Future readers won't necessarily know this.
**The `#[expect(unused)]` is removed in patch 3** -- fine, but introducing a dead-code function in one patch just to use it in the next is slightly awkward for bisection. The function has no callers between patches 2 and 3. Not a blocker.
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-06-04 1:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 19:42 [PATCH v17 0/6] Rust bindings for gem shmem Lyude Paul
2026-06-03 19:42 ` [PATCH v17 1/6] rust: drm: gem: shmem: Fix Default implementation for ObjectConfig Lyude Paul
2026-06-04 1:29 ` Claude review: " Claude Code Review Bot
2026-06-03 19:42 ` [PATCH v17 2/6] rust: drm: gem: shmem: Add DmaResvGuard helper Lyude Paul
2026-06-04 1:29 ` Claude Code Review Bot [this message]
2026-06-03 19:42 ` [PATCH v17 3/6] rust: drm: gem: shmem: Add vmap functions Lyude Paul
2026-06-04 1:29 ` Claude review: " Claude Code Review Bot
2026-06-03 19:42 ` [PATCH v17 4/6] rust: faux: Allow retrieving a bound Device Lyude Paul
2026-06-04 1:29 ` Claude review: " Claude Code Review Bot
2026-06-03 19:42 ` [PATCH v17 5/6] rust: sync: Add SetOnce::reset() Lyude Paul
2026-06-04 1:29 ` Claude review: " Claude Code Review Bot
2026-06-03 19:42 ` [PATCH v17 6/6] rust: drm: gem: Introduce shmem::Object::sg_table() Lyude Paul
2026-06-04 1:29 ` Claude review: " Claude Code Review Bot
2026-06-04 1:29 ` Claude review: Rust bindings for gem shmem Claude Code Review Bot
-- strict thread matches above, loose matches on Subject: below --
2026-06-04 19:24 [PATCH v18 0/4] " Lyude Paul
2026-06-04 19:24 ` [PATCH v18 1/4] rust: drm: gem: shmem: Add DmaResvGuard helper Lyude Paul
2026-06-04 20:03 ` 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-patch2-20260603195210.693856-3-lyude@redhat.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