From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: misc/syncobj: add new device
Date: Mon, 18 May 2026 16:53:32 +1000 [thread overview]
Message-ID: <review-patch12-20260516-jorth-syncobj-v1-12-88ede9d98a81@gmail.com> (raw)
In-Reply-To: <20260516-jorth-syncobj-v1-12-88ede9d98a81@gmail.com>
Patch Review
This is the main patch. Creates `/dev/syncobj` as a misc device with mode `0666`.
**Concerns:**
1. **No `compat_ioctl` struct padding verification**: The structures look well-aligned (all fields are naturally aligned, no implicit padding), and `compat_ptr_ioctl` is used. This should be fine.
2. **ioctl number**: Using `0xCD` which overlaps with the dead reiserfs range. The patch adds `0xCD 00-0F` to `ioctl-number.rst` right after the `0xCD 01` dead entry. This should work but could be confusing. Consider choosing a less ambiguous range.
3. **`mode = 0666`**: World-readable/writable. This is intentional since syncobjs are meant to be available to unprivileged users, similar to `/dev/dri/renderD*`. Fine for the use case.
4. **Missing `SYNCOBJ_IOC_QUERY` direction**: The query ioctl writes results back to userspace (via `copy_to_user` in `drm_syncobj_query`) but is declared as `_IOW` not `_IOWR`:
```c
#define SYNCOBJ_IOC_QUERY _IOW(SYNCOBJ_IOC_BASE, 4, struct syncobj_array_args)
```
Since the `points` field is a pointer to a user buffer (not the struct itself), this is technically acceptable (the struct itself is only read), but it's misleading. The same argument applies to `SYNCOBJ_IOC_SIGNAL` which also reads points from userspace through the pointer.
5. **No selftests**: A new UAPI should come with `tools/testing/selftests/` tests.
6. **`syncobj_ioctl_wait` returns `timeout` directly when negative**: `drm_syncobj_array_wait_timeout()` returns a negative `signed long` on error (e.g., `-ERESTARTSYS`). The code `if (timeout < 0) return timeout;` truncates `signed long` to `int` on 64-bit platforms. In practice the errno values fit in `int`, but this is technically a type narrowing.
7. **Module dependency on DRM**: The Kconfig has `depends on DRM` which is correct since it uses `drm_syncobj_*` functions. But if DRM is built as a module and this is also a module, the module loading order needs to be correct. `module_misc_device` handles init, but there's no explicit `MODULE_SOFTDEP` or similar.
8. **`syncobj_wait_args.pad` check**: Good -- the pad field is validated to be zero. However, `syncobj_sync_file_args` has no pad or flags field, meaning there's no reserved space for future extension of the export/import ioctls. Consider adding a `__u32 flags; __u32 pad;` to `syncobj_sync_file_args`.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-18 6:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-16 11:06 [PATCH 00/12] misc/syncobj: add /dev/syncobj device Julian Orth
2026-05-16 11:06 ` [PATCH 01/12] drm/syncobj: add drm_syncobj_from_fd Julian Orth
2026-05-18 6:53 ` Claude review: " Claude Code Review Bot
2026-05-16 11:06 ` [PATCH 02/12] drm/syncobj: add drm_syncobj_fence_lookup Julian Orth
2026-05-18 6:53 ` Claude review: " Claude Code Review Bot
2026-05-16 11:06 ` [PATCH 03/12] drm/syncobj: make drm_syncobj_array_wait_timeout public Julian Orth
2026-05-18 6:53 ` Claude review: " Claude Code Review Bot
2026-05-16 11:06 ` [PATCH 04/12] drm/syncobj: add drm_syncobj_register_eventfd Julian Orth
2026-05-18 6:53 ` Claude review: " Claude Code Review Bot
2026-05-16 11:06 ` [PATCH 05/12] drm/syncobj: have transfer functions accept drm_syncobj directly Julian Orth
2026-05-18 6:53 ` Claude review: " Claude Code Review Bot
2026-05-16 11:06 ` [PATCH 06/12] drm/syncobj: add drm_syncobj_transfer Julian Orth
2026-05-18 6:53 ` Claude review: " Claude Code Review Bot
2026-05-16 11:06 ` [PATCH 07/12] drm/syncobj: add drm_syncobj_timeline_signal Julian Orth
2026-05-18 6:53 ` Claude review: " Claude Code Review Bot
2026-05-16 11:06 ` [PATCH 08/12] drm/syncobj: add drm_syncobj_query Julian Orth
2026-05-18 6:53 ` Claude review: " Claude Code Review Bot
2026-05-16 11:06 ` [PATCH 09/12] drm/syncobj: fix resource leak in drm_syncobj_import_sync_file_fence Julian Orth
2026-05-18 6:53 ` Claude review: " Claude Code Review Bot
2026-05-16 11:06 ` [PATCH 10/12] drm/syncobj: add drm_syncobj_import_sync_file Julian Orth
2026-05-18 6:53 ` Claude review: " Claude Code Review Bot
2026-05-16 11:06 ` [PATCH 11/12] drm/syncobj: add drm_syncobj_export_sync_file Julian Orth
2026-05-18 6:53 ` Claude review: " Claude Code Review Bot
2026-05-16 11:06 ` [PATCH 12/12] misc/syncobj: add new device Julian Orth
2026-05-16 11:37 ` Greg Kroah-Hartman
2026-05-16 11:38 ` Greg Kroah-Hartman
2026-05-16 12:08 ` Julian Orth
2026-05-18 6:53 ` Claude Code Review Bot [this message]
2026-05-18 6:53 ` Claude review: misc/syncobj: add /dev/syncobj device 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-patch12-20260516-jorth-syncobj-v1-12-88ede9d98a81@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