[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [PATCH v2 0/4] 9pfs: handle transport errors
From: |
Greg Kurz |
Subject: |
[Qemu-devel] [PATCH v2 0/4] 9pfs: handle transport errors |
Date: |
Thu, 27 Apr 2017 11:45:32 +0200 |
User-agent: |
StGit/0.17.1-20-gc0b1b-dirty |
The 9p protocol relies on a reliable transport, but the current code
treats transport errors (ie, failure to marshal or unmarshal) as if
they were coming from the backend. This doesn't make sense: if the
transport failed, we should notify the guest that the transport is
broken and needs to be reset, using transport specific means.
This series modifies the existing virtio-9p transport so that it can
notify the guest about transport failures. The core 9p code is modified
as well so that it stops handling requests when the transport fails.
Changes since v1:
- dropped the "virtio: Error object based virtio_error()" patch
- see patches for detailed changes
--
Greg
---
Greg Kurz (4):
fsdev: don't allow unknown format in marshal/unmarshal
9pfs: drop pdu_push_and_notify()
virtio-9p: factor out virtio_9p_error_err()
9pfs: handle broken transport
fsdev/9p-iov-marshal.c | 4 ++-
hw/9pfs/9p.c | 52 ++++++++++++++++++++++++++++++++------------
hw/9pfs/9p.h | 1 +
hw/9pfs/virtio-9p-device.c | 51 +++++++++++++++++++++++++++++--------------
4 files changed, 75 insertions(+), 33 deletions(-)
- [Qemu-devel] [PATCH v2 0/4] 9pfs: handle transport errors,
Greg Kurz <=
- [Qemu-devel] [PATCH v2 1/4] fsdev: don't allow unknown format in marshal/unmarshal, Greg Kurz, 2017/04/27
- [Qemu-devel] [PATCH v2 2/4] 9pfs: drop pdu_push_and_notify(), Greg Kurz, 2017/04/27
- [Qemu-devel] [PATCH v2 3/4] virtio-9p: factor out virtio_9p_error_err(), Greg Kurz, 2017/04/27
- [Qemu-devel] [PATCH v2 4/4] 9pfs: handle broken transport, Greg Kurz, 2017/04/27
- Re: [Qemu-devel] [PATCH v2 0/4] 9pfs: handle transport errors, no-reply, 2017/04/27