From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54063) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yqfqs-0004ZI-BK for qemu-devel@nongnu.org; Fri, 08 May 2015 06:49:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yqfqk-0002DV-Ph for qemu-devel@nongnu.org; Fri, 08 May 2015 06:49:54 -0400 Date: Fri, 8 May 2015 12:49:43 +0200 From: Kevin Wolf Message-ID: <20150508104943.GF4318@noname.redhat.com> References: <1430915026-19156-1-git-send-email-famz@redhat.com> <554A56FD.2080702@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <554A56FD.2080702@redhat.com> Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] vmdk: Fix next_cluster_sector for compressed write List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Max Reitz Cc: Fam Zheng , qemu-devel@nongnu.org, qemu-block@nongnu.org, qemu-stable@nongnu.org Am 06.05.2015 um 20:01 hat Max Reitz geschrieben: > On 06.05.2015 14:23, Fam Zheng wrote: > >This fixes the bug introduced by commit c6ac36e (vmdk: Optimize cluster > >allocation). > > > >Sometimes, write_len could be larger than cluster size, because it > >contains both data and marker. We must advance next_cluster_sector in > >this case, otherwise the image gets corrupted. > > > >Reported-by: Antoni Villalonga > >Signed-off-by: Fam Zheng > > Reviewed-by: Max Reitz Thanks, added a "Cc: qemu-stable@nongnu.org" line to the commit message and applied to the block branch. Kevin