From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nisij-0005hW-8T for qemu-devel@nongnu.org; Sat, 20 Feb 2010 12:02:21 -0500 Received: from [199.232.76.173] (port=44837 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nisii-0005hM-E6 for qemu-devel@nongnu.org; Sat, 20 Feb 2010 12:02:20 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1Nisig-00008d-Qg for qemu-devel@nongnu.org; Sat, 20 Feb 2010 12:02:20 -0500 Received: from mail-yx0-f200.google.com ([209.85.210.200]:60206) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Nisig-00008M-EP for qemu-devel@nongnu.org; Sat, 20 Feb 2010 12:02:18 -0500 Received: by yxe38 with SMTP id 38so1122832yxe.4 for ; Sat, 20 Feb 2010 09:02:18 -0800 (PST) Message-ID: <4B801595.9030408@codemonkey.ws> Date: Sat, 20 Feb 2010 11:02:13 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH 0/3] qcow2: Rewrite alloc_refcount_block References: <1266250769-5816-1-git-send-email-kwolf@redhat.com> <4B7EFEFA.60501@codemonkey.ws> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Juan Quintela Cc: Kevin Wolf , hch@lst.de, armbru@redhat.com, gleb@redhat.com, qemu-devel@nongnu.org On 02/19/2010 07:49 PM, Juan Quintela wrote: > Anthony Liguori wrote: > >> On 02/15/2010 10:19 AM, Kevin Wolf wrote: >> >>> The current implementation of alloc_refcount_block and grow_refcount_table has >>> fundamental problems regarding error handling. There are some places where an >>> I/O error means that the image is going to be corrupted. I have found that the >>> only way to fix this is to completely rewrite the thing. >>> >>> Just sending as an RFC to the list hasn't generated a lot of comments (to be >>> precise, not a single one). This is a critical part of qcow2 and needs reviews. >>> So let's try it another way: People in CC, please give it a review. Sooner or >>> later some of you will need to do so anyway. >>> >>> >> Should I apply this series? I still don't see any review comments. >> > I sent review comments on the 18th. I expect Kevin to address them. I > talked with him on irc while doing the review (i.e. he knows about > them). > You're right, I missed it. Thanks. Regards, Anthony Liguori > Kevin??? > > Later, Juan. > > > >