linux-kernel - Re: XD/smartmedia - how to implement it right?

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: <200912071613.43421.arnd@arndb.de>
Date:	Mon, 7 Dec 2009 16:13:43 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	Maxim Levitsky <maximlevitsky@...il.com>
Cc:	Pavel Machek <pavel@....cz>, Alex Dubov <oakad@...oo.com>,
	"J?rn Engel" <joern@...fs.org>,
	"linux-kernel" <linux-kernel@...r.kernel.org>
Subject: Re: XD/smartmedia - how to implement it right?

On Sunday 06 December 2009, Maxim Levitsky wrote:
> Supporting wear leveling in hardware is easier, because this way, they
> can be sure it works well, and not depend on each and every driver
> implementation to do that right.

Assuming that hardware engineers know what they are doing, yes.
Unfortunately the hardware people seem to be just as clueless about
this as the every device driver writer, which actually makes this much
worse. Having bad wear leveling in hardware often means that the
card eats your data, no matter what the driver does. Doing it in software
means that it's broken most of the time but fixable.

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