From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: [PATCH 00/17] blktap2 related bugfix patches Date: Mon, 27 Oct 2014 14:32:17 -0400 Message-ID: <20141027183217.GA13854@laptop.dumpdata.com> References: <1413252845-23433-1-git-send-email-wency@cn.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <1413252845-23433-1-git-send-email-wency@cn.fujitsu.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Wen Congyang Cc: Ian Campbell , Ian Jackson , Jiang Yunhong , Dong Eddie , xen devel , Yang Hongyang , Lai Jiangshan List-Id: xen-devel@lists.xenproject.org On Tue, Oct 14, 2014 at 10:13:48AM +0800, Wen Congyang wrote: > These bugs are found when we implement COLO, or rebase > COLO to upstream xen. They are independent patches, so > post them in separate series. There is no maintainer for blktap in the Xen code-base. As such there is nobody to actually review the patches. Now there is an version of blktap(v3?v4?) 'userspace' that I have been hearing from but I do not know much about. As such - I was wondering what should be done about your changes to blktap? Are you considering being the maintainer of this version of blktap code? > > The codes are also hosted on github: > https://github.com/wencongyang/xen/commits/bugfix-v4 > > Lai Jiangshan (1): > tools: blktap2: dynamic allocate aio_requests to avoid -EBUSY error > > Wen Congyang (16): > tools: block-remus: pass uuid to the callback td_open > tools: block-remus: use correct way to get remus_image > tools: block-remus: fix bug in tdremus_close() > tools: block-remus: fix memory leak > tools: blktap2: return the correct dev path > tools: blktap2: use correct way to get free event id > tools: blktap2: don't return negative event id > tools: blktap2: use correct way to define array. > tools: block-remus: fix bug in ctl_request() > tools: block-remus: clean unused functions > tools: blktap2: implement an API to create a connection asynchronously > tools: block-remus: connect to backup asynchronously > block-remus: switch to unprotected mode before closing > tools: blktap2: move ramdisk related codes to block-replication.c > support blktap remus in xl > HACK: libxl/remus: setup and control disk replication for blktap2 > backends > > tools/blktap2/drivers/Makefile | 1 + > tools/blktap2/drivers/block-aio.c | 41 +- > tools/blktap2/drivers/block-cache.c | 4 +- > tools/blktap2/drivers/block-log.c | 4 +- > tools/blktap2/drivers/block-qcow.c | 5 +- > tools/blktap2/drivers/block-ram.c | 5 +- > tools/blktap2/drivers/block-remus.c | 1201 +++++++---------------------- > tools/blktap2/drivers/block-replication.c | 928 ++++++++++++++++++++++ > tools/blktap2/drivers/block-replication.h | 178 +++++ > tools/blktap2/drivers/block-vhd.c | 5 +- > tools/blktap2/drivers/scheduler.c | 33 +- > tools/blktap2/drivers/tapdisk-control.c | 17 +- > tools/blktap2/drivers/tapdisk-disktype.c | 12 +- > tools/blktap2/drivers/tapdisk-disktype.h | 2 +- > tools/blktap2/drivers/tapdisk-interface.c | 21 +- > tools/blktap2/drivers/tapdisk-interface.h | 1 + > tools/blktap2/drivers/tapdisk-vbd.c | 9 + > tools/blktap2/drivers/tapdisk-vbd.h | 1 + > tools/blktap2/drivers/tapdisk.h | 3 +- > tools/libxl/Makefile | 2 +- > tools/libxl/libxl.c | 25 +- > tools/libxl/libxl_blktap2.c | 38 +- > tools/libxl/libxl_create.c | 8 + > tools/libxl/libxl_device.c | 35 +- > tools/libxl/libxl_dm.c | 4 +- > tools/libxl/libxl_internal.h | 10 +- > tools/libxl/libxl_noblktap2.c | 8 +- > tools/libxl/libxl_remus_device.c | 6 + > tools/libxl/libxl_remus_disk_blktap.c | 209 +++++ > tools/libxl/libxl_types.idl | 2 + > tools/libxl/libxlu_disk_l.l | 2 + > 31 files changed, 1857 insertions(+), 963 deletions(-) > create mode 100644 tools/blktap2/drivers/block-replication.c > create mode 100644 tools/blktap2/drivers/block-replication.h > create mode 100644 tools/libxl/libxl_remus_disk_blktap.c > > -- > 1.9.3 > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel