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: <2c0942db0904061504l6504934bi446f7425fcd38470@mail.gmail.com>
Date:	Mon, 6 Apr 2009 15:04:05 -0700
From:	Ray Lee <ray-lk@...rabbit.org>
To:	Hua Zhong <hzhong@...il.com>
Cc:	Theodore Tso <tytso@....edu>,
	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 6, 2009 at 2:35 PM, Hua Zhong <hzhong@...il.com> wrote:
>> 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.
>
> I am not talking about "most" people's complaints. There are use cases for
> ext3 far beyond the desktop.
>
> I worked on a user-space library on top of ext3 before on embedded systems.
> It may not have been the case for me but I could well imagine where it could
> get too clever and depend upon "ordered".

Speaking as another embedded Linux guy, I don't update kernels on my
embedded platforms willy-nilly, nor do I design a library that relies
upon some default behavior without specifying it explicitly. That's
just one of the prices of doing embedded development.

Your argument seems to be that someone may be relying upon default
kernel behavior and, at the same time, is willing to continually
upgrade their kernel. I'd argue that person is, y'know, nuts. If
they're willing to upgrade their kernel on something that has that
stringent of requirements, then they should be willing to force a
mount option at the same time.

If they're willing to upgrade their kernel blindly, then they
shouldn't be doing embedded development.
--
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/