linux-kernel - Re: [PATCH V2] UBI: power cut emulation for testing

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <55219677.6090900@nod.at>
Date:	Sun, 05 Apr 2015 22:09:27 +0200
From:	Richard Weinberger <richard@....at>
To:	Pavel Machek <pavel@....cz>
CC:	david.oberhollenzer@...ma-star.at,
	"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V2] UBI: power cut emulation for testing

Am 05.04.2015 um 22:04 schrieb Pavel Machek:
> On Sun 2015-04-05 21:49:27, Richard Weinberger wrote:
>> On Sun, Apr 5, 2015 at 9:31 PM, Pavel Machek <pavel@....cz> wrote:
>>> On Thu 2015-03-26 23:59:50, david.oberhollenzer@...ma-star.at wrote:
>>>> Emulate random power cuts by switching device to ro after a number of
>>>> writes to allow simple power cut testing with nand-sim.
>>>>
>>>> Maximum and minimum number of successful writes before power cut and
>>>> what kind of writes (EC header, VID header or none) to interrupt
>>>> configurable via debugfs.
>>>>
>>>> Signed-off-by: David Oberhollenzer <david.oberhollenzer@...ma-star.at>
>>>> ---
>>>> V2: Remove broken check to prevent multiple triggering
>>>
>>> Does NAND always finish write of full block during powerfail?
>>
>> Not sure if I correctly understand your question.
>> Unless you don't have special hardware a write can be interrupted and
>> can cause problems.
> 
> But this only emulates fail after a full block written, no?

Emulating all aspects of real hardware is almost impossible.

Thanks,
//richard
--
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/