linux-kernel - [PATCH RFC] Ext3 data=guarded

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1252422595-4554-1-git-send-email-chris.mason@oracle.com>
Date:	Tue,  8 Sep 2009 11:09:53 -0400
From:	Chris Mason <chris.mason@...cle.com>
To:	jack@...e.cz, tytso@....edu, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org
Subject: [PATCH RFC] Ext3 data=guarded

Hello everyone,

Here is a respin of the ext3 data=guarded code.  This adds a new mount option
(mount -o data=guarded) to prevent garbage in files after a crash.

The main difference from data=ordered is that data=guarded only updates
the on disk i_size after all of the data blocks are on disk.  This allows
us to avoid flushing all the data pages down to disk with every commit.

More details are in the patch emails.  It has survived some long stress tests,
but I do still need to hammer on O_DIRECT and hole filling.

Jan Kara has already picked up patch 1/2, but I'm including it here in case
anyone wants to test the code.

One important part of this patch series is that it tries to have minimal
impact on the other data modes of ext3.  So, data=ordered and data=writeback
should stay the same in performance and reliability with this code.

-chris

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/