diff options
| author |   David Hildenbrand <david@redhat.com> | 2024-02-13 14:54:25 +0100 |
|---|---|---|
| committer |   Michael S. Tsirkin <mst@redhat.com> | 2024-03-19 02:45:49 -0400 |
| commit | 310227f42882c52356b523e2f4e11690eebcd2ab (patch) | |
| tree | 4223390e49a56081b5572803e177d33828bc798a /drivers/virtio/virtio.c | |
| parent | vdpa_sim: reset must not run (diff) | |
| download | wireguard-linux-310227f42882c52356b523e2f4e11690eebcd2ab.tar.xz wireguard-linux-310227f42882c52356b523e2f4e11690eebcd2ab.zip | |
virtio: reenable config if freezing device failed
Currently, we don't reenable the config if freezing the device failed.
For example, virtio-mem currently doesn't support suspend+resume, and
trying to freeze the device will always fail. Afterwards, the device
will no longer respond to resize requests, because it won't get notified
about config changes.
Let's fix this by re-enabling the config if freezing fails.
Fixes: 22b7050a024d ("virtio: defer config changed notifications")
Cc: <stable@kernel.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>
Cc: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Signed-off-by: David Hildenbrand <david@redhat.com>
Message-Id: <20240213135425.795001-1-david@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to '')
| -rw-r--r-- | drivers/virtio/virtio.c | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/drivers/virtio/virtio.c b/drivers/virtio/virtio.c index f4080692b351..f513ee21b1c1 100644 --- a/drivers/virtio/virtio.c +++ b/drivers/virtio/virtio.c @@ -510,8 +510,10 @@ int virtio_device_freeze(struct virtio_device *dev) if (drv && drv->freeze) { ret = drv->freeze(dev); - if (ret) + if (ret) { + virtio_config_enable(dev); return ret; + } } if (dev->config->destroy_avq) |