From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/virtio: abort virtqueue wait on device removal to avoid hung task
Date: Mon, 25 May 2026 21:05:48 +1000 [thread overview]
Message-ID: <review-overall-20260521-virtio-gpu_wait_event-v2-1-5796b3a71d03@redhat.com> (raw)
In-Reply-To: <20260521-virtio-gpu_wait_event-v2-1-5796b3a71d03@redhat.com>
Overall Series Review
Subject: drm/virtio: abort virtqueue wait on device removal to avoid hung task
Author: Ryosuke Yasuoka <ryasuoka@redhat.com>
Patches: 9
Reviewed: 2026-05-25T21:05:48.593126
---
This is a single-patch fix for a real syzbot-reported hung task bug in the virtio-gpu driver. The core problem is well understood: `wait_event()` calls in `virtio_gpu_queue_ctrl_sgs()` and `virtio_gpu_queue_cursor()` block indefinitely inside `drm_dev_enter()`/`drm_dev_exit()` SRCU critical sections. Since `drm_dev_unplug()` calls `synchronize_srcu()` which waits for those critical sections to complete, device removal and shutdown deadlock.
The v2 approach — a driver-level `vqs_released` flag set before `drm_dev_unplug()` — is the right idea and is a clear improvement over v1's arbitrary timeout. The abort paths correctly mirror the existing `drm_dev_enter()` failure cleanup. However, I have a few concerns about atomicity/ordering, and a potential race window that should be addressed.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-25 11:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 2:19 [PATCH v2] drm/virtio: abort virtqueue wait on device removal to avoid hung task Ryosuke Yasuoka
2026-05-21 2:19 ` syzbot
2026-05-21 2:19 ` syzbot
2026-05-21 19:01 ` Dmitry Osipenko
2026-05-21 19:02 ` syzbot
2026-05-21 19:02 ` syzbot
2026-05-22 8:51 ` Ryosuke Yasuoka
2026-05-22 8:51 ` syzbot
2026-05-22 8:51 ` syzbot
2026-05-25 11:05 ` Claude Code Review Bot [this message]
2026-05-25 11:05 ` 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-20260521-virtio-gpu_wait_event-v2-1-5796b3a71d03@redhat.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