From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57867) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bDRG4-0000rP-1t for qemu-devel@nongnu.org; Thu, 16 Jun 2016 02:58:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bDRG0-0004FA-Tt for qemu-devel@nongnu.org; Thu, 16 Jun 2016 02:58:32 -0400 Received: from mailhub.sw.ru ([195.214.232.25]:43569 helo=relay.sw.ru) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bDRG0-0004Dr-Fm for qemu-devel@nongnu.org; Thu, 16 Jun 2016 02:58:28 -0400 From: "Denis V. Lunev" Date: Thu, 16 Jun 2016 09:58:04 +0300 Message-Id: <1466060287-31514-1-git-send-email-den@openvz.org> Subject: [Qemu-devel] [PATCH 0/3] potentially broken drive-mirror/drive-backup in bdrv_co_discard List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org, qemu-block@nongnu.org Cc: den@openvz.org, Vladimir Sementsov-Ogievskiy , Stefan Hajnoczi , Fam Zheng , Kevin Wolf , Max Reitz Actually I have found this problem running iotest 132 for active async mirror I have sent yesturday. Anyway, the problem is actual for current backup/mirror implementation. bdrv_co_discard must mark areas dirty after writing zeroes, it must call before_write_notifier chain to push underlying data to backup and it also must properly fill tracked request information. Signed-off-by: Denis V. Lunev CC: Vladimir Sementsov-Ogievskiy CC: Stefan Hajnoczi CC: Fam Zheng CC: Kevin Wolf CC: Max Reitz