From: Xie Yongji <xieyongji@bytedance.com>
To: kwolf@redhat.com, stefanha@redhat.com
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: [PATCH 0/5] Some fixes and improvements for vduse-blk
Date: Mon, 13 Jun 2022 20:44:58 +0800 [thread overview]
Message-ID: <20220613124503.156-1-xieyongji@bytedance.com> (raw)
This series includes few fixes and improvements for the
vduse-blk export.
Patch 1 fixes resources leak when vduse fd is zero.
Patch 2, 3 fixes two bugs which could be triggered
by force deleting a vduse-blk export with high I/O loads.
Patch 4, 5 adds two new options for vduse-blk export.
Xie Yongji (5):
libvduse: Fix resources leak in vduse_dev_destroy()
vduse-blk: Don't unlink the reconnect file if device exists
vduse-blk: Don't delete the export until all inflight I/Os completed
vduse-blk: Add serial option
vduse-blk: Add name option
block/export/vduse-blk.c | 53 ++++++++++++++++++++++------
block/export/vhost-user-blk-server.c | 4 ++-
block/export/virtio-blk-handler.h | 2 +-
docs/tools/qemu-storage-daemon.rst | 5 +--
qapi/block-export.json | 11 +++---
storage-daemon/qemu-storage-daemon.c | 9 ++---
subprojects/libvduse/libvduse.c | 4 +--
7 files changed, 64 insertions(+), 24 deletions(-)
--
2.20.1
next reply other threads:[~2022-06-13 12:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 12:44 Xie Yongji [this message]
2022-06-13 12:44 ` [PATCH 1/5] libvduse: Fix resources leak in vduse_dev_destroy() Xie Yongji
2022-06-13 12:45 ` [PATCH 2/5] vduse-blk: Don't unlink the reconnect file if device exists Xie Yongji
2022-06-13 12:45 ` [PATCH 3/5] vduse-blk: Don't delete the export until all inflight I/Os completed Xie Yongji
2022-06-13 12:45 ` [PATCH 4/5] vduse-blk: Add serial option Xie Yongji
2022-06-13 12:45 ` [PATCH 5/5] vduse-blk: Add name option Xie Yongji
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=20220613124503.156-1-xieyongji@bytedance.com \
--to=xieyongji@bytedance.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).