From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: Introduce DRM_RAS using generic netlink for RAS
Date: Tue, 24 Feb 2026 10:45:41 +1000 [thread overview]
Message-ID: <review-overall-20260223060541.526397-7-riana.tauro@intel.com> (raw)
In-Reply-To: <20260223060541.526397-7-riana.tauro@intel.com>
Overall Series Review
Subject: Introduce DRM_RAS using generic netlink for RAS
Author: Riana Tauro <riana.tauro@intel.com>
Patches: 6
Reviewed: 2026-02-24T10:45:41.469510
---
This series introduces a DRM RAS (Reliability, Availability, Serviceability) infrastructure over generic netlink, allowing GPU drivers to expose error counters to userspace in a standardized way. Patch 1 creates the core DRM RAS framework with netlink operations (list-nodes, get-error-counter). Patches 2-3 add the Xe driver's integration layer, and patches 4-5 implement PVC-specific GT and SoC error handling that feeds into the RAS counters.
The overall architecture is reasonable: a global xarray of RAS nodes, a genl family with dump/do operations, and per-driver callbacks for querying error counters. The YAML-driven netlink spec and auto-generated headers follow modern kernel netlink conventions. The split between correctable and uncorrectable error nodes is a sensible design.
However, there are several concrete bugs in the series. The netlink dumpit handlers have uninitialized return values when their loops don't execute. The `doit_reply_value` function leaks an skb on one error path. The Xe registration cleanup has both a `kfree(ERR_PTR(...))` crash and a partial-registration leak that could lead to use-after-free if a later node registration fails. The correctable SoC error path in patch 5 clears status registers without reading or counting the errors, which seems inconsistent with the goal of error counting.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-02-24 0:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 6:05 [PATCH v8 0/5] Introduce DRM_RAS using generic netlink for RAS Riana Tauro
2026-02-23 6:05 ` [PATCH v8 1/5] drm/ras: Introduce the DRM RAS infrastructure over generic netlink Riana Tauro
2026-02-24 0:45 ` Claude review: " Claude Code Review Bot
2026-02-23 6:05 ` [PATCH v8 2/5] drm/xe/xe_drm_ras: Add support for XE DRM RAS Riana Tauro
2026-02-24 0:45 ` Claude review: " Claude Code Review Bot
2026-02-23 6:05 ` [PATCH v8 3/5] drm/xe/xe_hw_error: Integrate DRM RAS with hardware error handling Riana Tauro
2026-02-24 0:45 ` Claude review: " Claude Code Review Bot
2026-02-23 6:05 ` [PATCH v8 4/5] drm/xe/xe_hw_error: Add support for Core-Compute errors Riana Tauro
2026-02-24 0:45 ` Claude review: " Claude Code Review Bot
2026-02-23 6:05 ` [PATCH v8 5/5] drm/xe/xe_hw_error: Add support for PVC SoC errors Riana Tauro
2026-02-24 0:45 ` Claude review: " Claude Code Review Bot
2026-02-24 0:45 ` Claude Code Review Bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-28 8:08 [PATCH v9 0/5] Introduce DRM_RAS using generic netlink for RAS Riana Tauro
2026-03-03 4:32 ` Claude review: " Claude Code Review Bot
2026-03-04 7:44 [PATCH v10 0/5] " Riana Tauro
2026-03-05 3:47 ` 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-20260223060541.526397-7-riana.tauro@intel.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