linux-ext4 - Re: ext4 settings in an embedded system

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: <1353321735.20111.34.camel@sauron.fi.intel.com>
Date:	Mon, 19 Nov 2012 12:42:15 +0200
From:	Artem Bityutskiy <dedekind1@...il.com>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	Andrey Sidorov <qrxd43@...orola.com>,
	"Ohlsson, Fredrik (GE Healthcare, consultant)" 
	<Fredrik.Ohlsson@...com>, linux-ext4@...r.kernel.org
Subject: Re: ext4 settings in an embedded system

On Fri, 2012-11-16 at 09:40 -0600, Eric Sandeen wrote:
> Barriers were not made default on ext3 until 2011, in kernel v3.1,
> astonishingly.  So it makes sense that ext3 fared worse than ext4.

Very probable, I do not remember if we had them. But we were testing on
top of eMMC with not write-cache.

Anyway, that was long time ago.

While on it, one problem I remember in an unrelated testing of ext3 on
top of eMMC was related to _read_ errors. Sometimes after an power cut
eMMC returned an ECC error, so a sector could be unreadable. But after
writing to this sector it became fine.

ext3 and the tools treated a read error as fatal. However, in case of
eMMC that was something "normal".

I do not know how the situation changes since then, this was probably in
2009.

-- 
Best Regards,
Artem Bityutskiy

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)