Thread (8 messages) flat view 8 messages, 4 authors, 2026-08-04

Re: [PATCH v3 0/2] vsock/virtio: fix worker access after virtqueue teardown

From: Stefano Garzarella <sgarzare@redhat.com>
Date: 2026-08-04 09:45:42
Also in: kvm, lkml, netdev

On Wed, Jul 29, 2026 at 12:16:53PM -0700, Weiming Shi wrote:
Virtio-vsock workers can remain queued while freeze deletes the
virtqueues.  This series prevents workers delayed across freeze and
restore from retaining pointers to deleted queues, and prevents the RX
worker from refilling its queue after teardown.

Changes in v3:
- Resend the series with proper email threading; no code changes.

Changes in v2:
- Split the worker pointer changes from the RX refill fix because they
 fix different commits.
- Use bd50c5dc182b as the Fixes tag for the worker pointer changes.
- Keep b917507e5ad9 as the Fixes tag for the RX refill fix.
- Use the suggested out_nofill label when rx_run is clear.
Thanks, it's already queued but sice you fixed all my comments, just for 
record:

Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help