From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: JFYI: ext4 bug triggerable by kvm Date: Tue, 17 Aug 2010 12:23:01 +0300 Message-ID: <4C6A54F5.2090805@redhat.com> References: <4C694483.5010903@msgid.tls.msk.ru> <4C694E7D.3060600@codemonkey.ws> <20100816184237.GA16579@infradead.org> <4C69A0C4.2080102@codemonkey.ws> <20100817090755.GA11110@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Anthony Liguori , Michael Tokarev , KVM list , Kevin Wolf To: Christoph Hellwig Return-path: Received: from mx1.redhat.com ([209.132.183.28]:28135 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754187Ab0HQJYD (ORCPT ); Tue, 17 Aug 2010 05:24:03 -0400 In-Reply-To: <20100817090755.GA11110@infradead.org> Sender: kvm-owner@vger.kernel.org List-ID: On 08/17/2010 12:07 PM, Christoph Hellwig wrote: > > In short it's completely worthless for any real filesystem. > The documentation should be updated then. It suggests that it is usable for data integrity. (or maybe, it should be fixed?) -- error compiling committee.c: too many arguments to function