Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934422AbZDAWAe (ORCPT ); Wed, 1 Apr 2009 18:00:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S934301AbZDAWAV (ORCPT ); Wed, 1 Apr 2009 18:00:21 -0400 Received: from ey-out-2122.google.com ([74.125.78.26]:53706 "EHLO ey-out-2122.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756267AbZDAWAT (ORCPT ); Wed, 1 Apr 2009 18:00:19 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; b=oU/dR2Ca01X4ples/iRf83/SlZgPdcJVGmENiAfSF4b1XqrXS23pCGZFnt80NcA/R3 W5/fU/mkdUma8MoqkzPfMPoWiyF6Buw7gMMBTP3f9jwBVVAle/oqu4sHNzt57dQDq5P1 9QbVd8sdUM5gqbWCvwIlR9H4uoJ+qxaciZpr0= From: Harald Arnesen To: david@lang.hm Cc: Bill Davidsen , linux-kernel@vger.kernel.org Subject: Re: Linux 2.6.29 References: <49CD7B10.7010601@garzik.org> <49CD891A.7030103@rtr.ca> <49CD9047.4060500@garzik.org> <49CE2633.2000903@s5r6.in-berlin.de> <49CE3186.8090903@garzik.org> <49CE35AE.1080702@s5r6.in-berlin.de> <49CE3F74.6090103@rtr.ca> <20090329231451.GR26138@disturbed> <20090330003948.GA13356@mit.edu> <49D0710A.1030805@ursus.ath.cx> <49D3954A.9010309@tmr.com> Date: Thu, 02 Apr 2009 00:00:04 +0200 In-Reply-To: (david@lang.hm's message of "Wed, 1 Apr 2009 13:15:34 -0700 (PDT)") Message-ID: <87hc183uhn.fsf@basilikum.skogtun.org> User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/22.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1311 Lines: 27 david@lang.hm writes: >> Understood that it's not deliberate just careless. The two behaviors >> which are reported are (a) updating a record in an existing file and >> having the entire file content vanish, and (b) finding some one >> else's old data in my file - a serious security issue. I haven't >> seen any report of the case where a process unlinks or truncates a >> file, the disk space gets reused, and then the systems fails before >> the metadata is updated, leaving the data written by some other >> process in the file where it can be read - another possible security >> issue. > > ext3 eliminates this security issue by writing the data before the > metadata. ext4 (and I thing XFS) eliminate this security issue by not > allocating the blocks until it goes to write the data out. I don't > know how other filesystems deal with this. I've been wondering about that during the last days. How abut JFS and data loss (files containing zeroes after a crash), as compared to ext3, ext4, ordered and writeback journal modes? Is is safe? -- Hilsen Harald. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/