linux-kernel - Re: EXT3 File System Corruption 2.6.34

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 8 Jun 2010 07:14:03 -0400
From:	Theodore Tso <tytso@....EDU>
To:	Jeffrey Merkey <jeffmerkey@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: EXT3 File System Corruption 2.6.34

On Jun 7, 2010, at 10:14 PM, Jeffrey Merkey wrote:

> From: Jeffrey Merkey <jeffmerkey@...il.com>
> Date: Mon, Jun 7, 2010 at 8:13 PM
> Subject: Re: EXT3 File System Corruption 2.6.34
> To: Eric Sandeen <sandeen@...deen.net>
> 
> 
> Well, I will set this as default from now on.  Tell Evil Emperor Linus
> to put the fucking thing back the way it was so default kernel builds
> are not fucked up.

If you pull the plug without fsyncing the file, you will end up with a zero-length file -- or possibly no file at all, even with data=ordered.  If you really want to preserve data after pulling the power cord immediately after a write were the application hasn't done an fsync() or a sync() call, you can mount the file system with the mount option -o sync --- but then the performance will be horrible.

It's all a tradeoff of what you think is important....

-- Ted

--
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/