public inbox for drm-ai-reviews@public-inbox.freedesktop.org
 help / color / mirror / Atom feed
From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: Avoid oops on illegal VGA register access
Date: Wed, 18 Feb 2026 06:51:00 +1000	[thread overview]
Message-ID: <review-overall-20260217165214.236482-1-Simon.Richter@hogyros.de> (raw)
In-Reply-To: <20260217165214.236482-1-Simon.Richter@hogyros.de>

Overall Series Review

Subject: Avoid oops on illegal VGA register access
Author: Simon Richter <Simon.Richter@hogyros.de>
Patches: 2
Reviewed: 2026-02-18T06:51:00.223518

---

This is a single-patch series that adds error handling for `vga_get_uninterruptible()` in the i915 VGA code. The stated motivation is to avoid oops on non-x86 platforms where VGA registers cannot be mapped, which would cause `vga_get()` to return `-ENODEV`. The patch modifies `intel_vga_get()` to propagate error codes, and `intel_vga_disable()` to handle them by skipping VGA register access and jumping to the MMIO-based VGA plane disable.

The patch is based on a tree that contains a refactoring of `intel_vga.c` (adding `intel_vga_get()`, `intel_vga_put()`, `intel_pci_set_io_decode()`, etc.) that has not yet landed in drm-next. The base commit `15658979e64a` is not present in drm-next. This means the patch cannot be applied on its own — it depends on a prerequisite refactoring series. The cover letter acknowledges this indirectly, mentioning that "complementary changes in vgaarb" are also needed, but the dependency on the i915 VGA refactoring series is not stated.

There are a few coding style issues and one incomplete aspect: the error handling is only added for `intel_vga_get()` within `intel_vga_disable()`, but if the underlying problem is that `vga_get_uninterruptible()` can fail on non-x86, this should also be considered for `intel_vga_reset_io_mem()` which similarly calls `vga_get_uninterruptible()` without checking the return value.

---
Generated by Claude Code Patch Reviewer

  parent reply	other threads:[~2026-02-17 20:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-17 16:51 [PATCH 0/1] Avoid oops on illegal VGA register access Simon Richter
2026-02-17 16:51 ` [PATCH 1/1] drm/i915: handle failure from vga_get Simon Richter
2026-02-17 20:51   ` Claude review: " Claude Code Review Bot
2026-02-17 20:51 ` Claude Code Review Bot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-06 15:23 [PATCH 5.3-6.19 0/1] Avoid oops on illegal VGA register access Simon Richter
2026-03-08 22:44 ` 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-20260217165214.236482-1-Simon.Richter@hogyros.de \
    --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