summaryrefslogtreecommitdiffstats
path: root/drivers/vdpa/vdpa.c
diff options
context:
space:
mode:
authorMichael S. Tsirkin <mst@redhat.com>2021-10-05 09:04:10 +0200
committerMichael S. Tsirkin <mst@redhat.com>2022-03-04 14:33:22 +0100
commit0e7174b9d5877130fec41fb4a16e0c2ee4958d44 (patch)
tree7936ce2d33c8b175413c6d257bb77853e4cb1d4f /drivers/vdpa/vdpa.c
parentvirtio: document virtio_reset_device (diff)
downloadlinux-0e7174b9d5877130fec41fb4a16e0c2ee4958d44.tar.xz
linux-0e7174b9d5877130fec41fb4a16e0c2ee4958d44.zip
virtio_console: break out of buf poll on remove
A common pattern for device reset is currently: vdev->config->reset(vdev); .. cleanup .. reset prevents new interrupts from arriving and waits for interrupt handlers to finish. However if - as is common - the handler queues a work request which is flushed during the cleanup stage, we have code adding buffers / trying to get buffers while device is reset. Not good. This was reproduced by running modprobe virtio_console modprobe -r virtio_console in a loop. Fix this up by calling virtio_break_device + flush before reset. Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1786239 Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'drivers/vdpa/vdpa.c')
0 files changed, 0 insertions, 0 deletions