From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/sched: Remove redundant entity->rq initialization and checks
Date: Thu, 04 Jun 2026 12:41:19 +1000 [thread overview]
Message-ID: <review-overall-20260602153339.43453-1-tvrtko.ursulin@igalia.com> (raw)
In-Reply-To: <20260602153339.43453-1-tvrtko.ursulin@igalia.com>
Overall Series Review
Subject: drm/sched: Remove redundant entity->rq initialization and checks
Author: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
Patches: 3
Reviewed: 2026-06-04T12:41:19.912219
---
This is a single-patch cleanup that removes dead code from the DRM scheduler. The analysis is correct: after commit 28c5bf28763d ("drm/sched: Disallow initializing entities with no schedulers"), `drm_sched_entity_init()` validates that `sched_list` is non-empty and non-NULL, then unconditionally sets `entity->rq = &sched_list[0]->rq`. No code path in the scheduler ever sets `entity->rq` back to NULL after init. Therefore, the NULL checks in `kill`, `flush`, and `job_init` are dead code.
The patch also correctly identifies a latent bug in the removed dead code: the `dev_err(job->sched->dev, ...)` in `drm_sched_job_init()` would dereference `job->sched` before it has been initialized — `job->sched` is only assigned later in `drm_sched_job_arm()`, and the `memset(job, 0, ...)` hasn't even run yet at that point, so `job->sched` is whatever garbage was in the caller's allocation.
The patch is correct and safe to apply, with one minor issue noted below.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-06-04 2:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 15:33 [PATCH] drm/sched: Remove redundant entity->rq initialization and checks Tvrtko Ursulin
2026-06-03 8:37 ` Philipp Stanner
2026-06-03 9:14 ` Tvrtko Ursulin
2026-06-04 2:41 ` Claude Code Review Bot [this message]
2026-06-04 2:41 ` 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-20260602153339.43453-1-tvrtko.ursulin@igalia.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