From: "Michael S. Tsirkin" <mst@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: den-plotnikov@yandex-team.ru, qemu-devel@nongnu.org,
qemu-block@nongnu.org, raphael.norwitz@nutanix.com
Subject: Re: [PATCH v2 0/6] vhost-user-blk: Error handling fixes during initialistion
Date: Fri, 14 May 2021 08:20:49 -0400 [thread overview]
Message-ID: <20210514082025-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20210429171316.162022-1-kwolf@redhat.com>
On Thu, Apr 29, 2021 at 07:13:10PM +0200, Kevin Wolf wrote:
> vhost-user-blk neglects for several properties to check whether the
> configured value is even compatible with the backend. This results
> sometimes in crashes because of buggy error handling code, and sometimes
> in devices that are presented differently to the guest than the backend
> would expect and that don't work properly therefore.
>
> This series fixes some of these bugs.
OK so where is this going? Kevin you said you will merge?
If so
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
> v2:
> - Fix error paths in realize() that didn't set errp
> - Added vhost_dev_cleanup() back in the error path (more faithful revert
> of 77542d43149)
>
> Kevin Wolf (6):
> vhost-user-blk: Make sure to set Error on realize failure
> vhost-user-blk: Don't reconnect during initialisation
> vhost-user-blk: Improve error reporting in realize
> vhost-user-blk: Get more feature flags from vhost device
> virtio: Fail if iommu_platform is requested, but unsupported
> vhost-user-blk: Check that num-queues is supported by backend
>
> include/hw/virtio/vhost.h | 2 +
> hw/block/vhost-user-blk.c | 85 ++++++++++++++-------------------------
> hw/virtio/vhost-user.c | 5 +++
> hw/virtio/virtio-bus.c | 5 +++
> 4 files changed, 42 insertions(+), 55 deletions(-)
>
> --
> 2.30.2
next prev parent reply other threads:[~2021-05-14 12:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 17:13 [PATCH v2 0/6] vhost-user-blk: Error handling fixes during initialistion Kevin Wolf
2021-04-29 17:13 ` [PATCH v2 1/6] vhost-user-blk: Make sure to set Error on realize failure Kevin Wolf
2021-05-03 17:12 ` Eric Blake
2021-05-03 17:24 ` Raphael Norwitz
2021-04-29 17:13 ` [PATCH v2 2/6] vhost-user-blk: Don't reconnect during initialisation Kevin Wolf
2021-05-03 17:01 ` Raphael Norwitz
2021-05-04 9:10 ` Kevin Wolf
2021-05-04 8:59 ` Michael S. Tsirkin
2021-05-04 9:27 ` Kevin Wolf
2021-05-04 9:44 ` Michael S. Tsirkin
2021-05-04 10:57 ` Kevin Wolf
2021-05-04 11:08 ` Michael S. Tsirkin
2021-04-29 17:13 ` [PATCH v2 3/6] vhost-user-blk: Improve error reporting in realize Kevin Wolf
2021-04-29 17:13 ` [PATCH v2 4/6] vhost-user-blk: Get more feature flags from vhost device Kevin Wolf
2021-04-29 17:13 ` [PATCH v2 5/6] virtio: Fail if iommu_platform is requested, but unsupported Kevin Wolf
2021-04-29 17:13 ` [PATCH v2 6/6] vhost-user-blk: Check that num-queues is supported by backend Kevin Wolf
2021-05-14 12:20 ` Michael S. Tsirkin [this message]
2021-05-14 16:24 ` [PATCH v2 0/6] vhost-user-blk: Error handling fixes during initialistion Kevin Wolf
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=20210514082025-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=den-plotnikov@yandex-team.ru \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=raphael.norwitz@nutanix.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;
as well as URLs for NNTP newsgroup(s).