Claude review: drm/virtio: Fix driver removal with disabled KMS

[Claude Code Review Bot <claude-review@example.com>]

Overall Series Review

Subject: drm/virtio: Fix driver removal with disabled KMS
Author: Dmitry Osipenko <dmitry.osipenko@collabora.com>
Patches: 1
Reviewed: 2026-06-05T06:30:56.726523

---

This is a single-patch fix for a kernel crash that occurs when the virtio-gpu driver is removed (unbound) while KMS support is disabled (`CONFIG_DRM_VIRTIO_GPU_KMS=n` or the device reports zero scanouts). The fix is correct in concept: when KMS is disabled, `dev->driver_features` has `DRIVER_MODESET | DRIVER_ATOMIC` cleared and `drmm_mode_config_init()` is never called, so calling `drm_atomic_helper_shutdown()` unconditionally accesses uninitialized mode_config state (uninitialized mutexes, zeroed list heads) and crashes.

The patch does **not apply cleanly** to current drm-next. The diff context shows `virtio_gpu_release_vqs(dev)` preceding `drm_dev_unplug(dev)` in `virtio_gpu_remove()`, but the current drm-next tree has no such call — the function is just `drm_dev_unplug` / `drm_atomic_helper_shutdown` / `virtio_gpu_deinit` / `drm_dev_put`. The author appears to have based this on a different tree version. A rebase is needed.

---
Generated by Claude Code Patch Reviewer