From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: rust: drm: gem: Introduce shmem::Object::sg_table()
Date: Wed, 27 May 2026 14:05:19 +1000 [thread overview]
Message-ID: <review-patch6-20260526212857.1158294-7-lyude@redhat.com> (raw)
In-Reply-To: <20260526212857.1158294-7-lyude@redhat.com>
Patch Review
**Status: Issues found, core design is sound**
The overall architecture is well-thought-out:
- `LazyInit<Devres<SGTableMap<T>>>` stores the devres-managed mapping
- `Devres` ensures revocation on driver-unbind
- `LazyInit` ensures one-time initialization
- The self-referential `NonNull<Object<T>>` in `SGTableMap` is safe because `Object` is pinned
**The `free_callback` reordering is correct and important:**
```rust
+ unsafe { Pin::new_unchecked(&mut (*this).sgt_res) }.reset();
+
+ unsafe { bindings::drm_gem_shmem_release(base) };
```
Resetting `sgt_res` before releasing the GEM object ensures the SGTable is freed while the GEM object is still valid. Then `drm_gem_shmem_release` sees `shmem->sgt == NULL` (set by `__drm_gem_shmem_free_sgt_locked`) and skips the now-unnecessary cleanup. No double-free.
**The `sg_table()` method is clean:**
```rust
+ pub fn sg_table<'a>(
+ &'a self,
+ dev: &'a device::Device<Bound>,
+ ) -> Result<&'a scatterlist::SGTable> {
+ if dev.as_raw() != self.dev().as_ref().as_raw() {
+ return Err(EINVAL);
+ }
+ match self.sgt_res.init(Devres::new(dev, SGTableMap::new(self))) {
+ Ok(ret) | Err(LazyInitError::AlreadyInit(ret)) => Ok(ret.access(dev)?),
+ Err(LazyInitError::DuringInit(e)) => Err(e),
+ }
+ }
```
The device identity check before `init` prevents creating a `Devres` bound to the wrong device. The `LazyInit::init` return handling correctly distinguishes first-init from already-init.
**Issue 1: Test type mismatch.** `create_drm_dev` takes `name: &'static CStr` but is called with `Some(c"Kunit")`:
```rust
+ fn create_drm_dev(
+ name: &'static CStr,
+ ) -> ...
+ let (dev, drm) = create_drm_dev(Some(c"Kunit"))?;
+ let (wrong_dev, wrong_drm) = create_drm_dev(Some(c"EvilKunit"))?;
```
`Some(c"Kunit")` is `Option<&'static CStr>`, not `&'static CStr`. This won't compile. Either the function signature should be `name: Option<&'static CStr>` (if a dependency changed `faux::Registration::new` to take optional name), or the calls should pass `c"Kunit"` directly without `Some()`.
**Issue 2: Unused variable.** `wrong_drm` is bound but never used:
```rust
+ let (wrong_dev, wrong_drm) = create_drm_dev(Some(c"EvilKunit"))?;
```
This will produce a compiler warning. Should be `_wrong_drm` or `_`.
**Minor: SGTableMap::new discards the sgt pointer.** This is intentional (using `drm_gem_shmem_get_pages_sgt` for its side effect of populating `shmem->sgt`), but a brief comment would help readers understand why the result of `from_err_ptr` is discarded:
```rust
+ fn new(obj: &Object<T>) -> impl Init<Self, Error> {
+ from_err_ptr(unsafe { bindings::drm_gem_shmem_get_pages_sgt(obj.as_raw_shmem()) })?;
+ Ok(Self { obj: obj.into() })
+ }
```
The `Send`/`Sync` impls for `SGTableMap` are justified by the GEM object's thread-safety guarantees.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-27 4:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 21:28 [PATCH v14 0/6] rust: drm: gem: shmem: Add sg_table() function Lyude Paul
2026-05-26 21:28 ` [PATCH v14 1/6] rust: faux: Allow retrieving a bound Device Lyude Paul
2026-05-27 4:05 ` Claude review: " Claude Code Review Bot
2026-05-26 21:28 ` [PATCH v14 2/6] rust: gem: shmem: Fix Default implementation for ObjectConfig Lyude Paul
2026-05-27 4:05 ` Claude review: " Claude Code Review Bot
2026-05-26 21:28 ` [PATCH v14 3/6] rust: drm: gem: s/device::Device/Device/ for shmem.rs Lyude Paul
2026-05-27 4:05 ` Claude review: " Claude Code Review Bot
2026-05-26 21:28 ` [PATCH v14 4/6] drm/gem/shmem: Introduce __drm_gem_shmem_free_sgt_locked() Lyude Paul
2026-05-27 4:05 ` Claude review: " Claude Code Review Bot
2026-05-26 21:28 ` [PATCH v14 5/6] rust: drm: gem/shmem: Add DmaResvGuard helper Lyude Paul
2026-05-27 4:05 ` Claude review: " Claude Code Review Bot
2026-05-26 21:28 ` [PATCH v14 6/6] rust: drm: gem: Introduce shmem::Object::sg_table() Lyude Paul
2026-05-27 4:05 ` Claude Code Review Bot [this message]
2026-05-27 4:05 ` Claude review: rust: drm: gem: shmem: Add sg_table() function 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-patch6-20260526212857.1158294-7-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