linux-kernel - Re: [PATCH 0/8][RFC] IO latency/throughput fixes

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]

Message-ID: <20090406211931.GB8586@mit.edu>
Date:	Mon, 6 Apr 2009 17:19:31 -0400
From:	Theodore Tso <tytso@....edu>
To:	Hua Zhong <hzhong@...il.com>
Cc:	'Linus Torvalds' <torvalds@...ux-foundation.org>,
	'Jens Axboe' <jens.axboe@...cle.com>,
	'Linux Kernel Mailing List' <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/8][RFC] IO latency/throughput fixes

On Mon, Apr 06, 2009 at 01:12:08PM -0700, Hua Zhong wrote:
> Grr..making writeback as default would break people's setup that relies on
> the ordered semantics, especially in the embedded world. It's a big no-no.

I've added workarounds for 2.6.30 that provide the replace-via-rename
and replace-via-truncate workarounds for ext3 data=writeback cases.
See commits e7c8f507 and f7ab34ea.  

There won't be an implied fsync for newly created files, yes, but you
could have crashed 5 seconds earlier, at which point you would have
lost the newly created file anyway.  Replace-via-rename and
replace-via-truncate solves the problem for applications which are
editing pre-existing files, which was most of people's complaints
about depending on data=ordered semantics.

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