From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: accel/rocket: fix ignored return value in rocket_ioctl_submit
Date: Sat, 16 May 2026 16:08:43 +1000 [thread overview]
Message-ID: <review-overall-20260510200047.6117-1-contact.kartikn@gmail.com> (raw)
In-Reply-To: <20260510200047.6117-1-contact.kartikn@gmail.com>
Overall Series Review
Subject: accel/rocket: fix ignored return value in rocket_ioctl_submit
Author: Kartik Nair <contact.kartikn@gmail.com>
Patches: 1
Reviewed: 2026-05-16T16:08:43.322827
---
This is a single-patch fix for the `accel/rocket` driver where `rocket_ioctl_submit()` was ignoring the return value of `rocket_ioctl_submit_job()`. The bug is real — without this fix, a failed job submission is silently swallowed and userspace receives a success return code despite the failure. The fix is correct, minimal, and follows the existing error-handling pattern already used in the same function (the `copy_from_user` loop above uses the identical `goto exit` pattern).
**Verdict: The patch looks good.**
One minor observation worth noting, but not necessarily a blocker: when a job fails partway through a multi-job submission, the jobs that were already successfully submitted (pushed to the scheduler) will still execute. This is arguably the correct behavior — `rocket_ioctl_submit_job()` fully owns each job's lifecycle (it cleans up on error, and pushes to the scheduler on success) — but the caller has no way to cancel previously submitted jobs. Whether this is a problem depends on the userspace API contract. The original code had the same issue (it submitted all jobs regardless of failures), so this patch is strictly an improvement.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-16 6:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 20:00 [PATCH] accel/rocket: fix ignored return value in rocket_ioctl_submit Kartik Nair
2026-05-16 6:08 ` Claude Code Review Bot [this message]
2026-05-16 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-20260510200047.6117-1-contact.kartikn@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