From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Martin K. Petersen" Subject: Re: [RFC] block integrity: Fix write after checksum calculation problem Date: Tue, 22 Feb 2011 11:45:44 -0500 Message-ID: References: <20110222020022.GH32261@tux1.beaverton.ibm.com> Mime-Version: 1.0 Content-Type: text/plain Cc: Jens Axboe , linux-kernel , linux-fsdevel@vger.kernel.org, Mingming Cao , linux-scsi To: djwong@us.ibm.com Return-path: Received: from rcsinet10.oracle.com ([148.87.113.121]:21320 "EHLO rcsinet10.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754509Ab1BVQsF (ORCPT ); Tue, 22 Feb 2011 11:48:05 -0500 In-Reply-To: <20110222020022.GH32261@tux1.beaverton.ibm.com> (Darrick J. Wong's message of "Mon, 21 Feb 2011 18:00:22 -0800") Sender: linux-fsdevel-owner@vger.kernel.org List-ID: >>>>> "Darrick" == Darrick J Wong writes: Darrick> Unfortunately, I didn't get a sense that any sort of consensus Darrick> had been reached We had a session on this topic at the storage workshop in Auguest. The consensus was that filesystems really need to handle this. Also, DIX is only the tip of the iceberg. Many other impending technologies feature checksums and require pages to be stable during I/O due to checksumming, encryption and so on. The VM is already trying to do the right thing. We just need the relevant filesystems to catch up. -- Martin K. Petersen Oracle Linux Engineering