Re: mtd/fs/jffs2 erase.c,1.84,1.85 roll back

[Anders Grafstrom <grfstrm@users.sourceforge.net>]

Artem B. Bityutskiy wrote:
> On Tue, 2005-09-20 at 21:49 +0200, Anders Grafstrom wrote:
> 
>>So if we return -EIO, then we go to jffs2_erase_failed(). For NAND, if 
>>the MTD driver reported erase failure (bad_offset != 0xffffffff), a 
>>retry is made before giving up on the block and marking it bad. Also the 
>>read operation may have failed, erase may have failed and MTD missed it, 
>>write of clean marker may have failed. As it is these cases will put the 
>>block on the bad_list. In the case of NOR it will also be put on the 
>>bad_list at once.
>>But how about retrying for all of these cases?
> 
> 
> Sorry, no more today. What does your patch do? Adds the second try? What
> for?
> 

jffs2 makes a second try if a failed erase is reported by the mtd 
driver. But only for NAND (in jffs2_write_nand_badblock()). What I'm 
after is a retry for NOR as well. But I wrote the patch so it would 
retry for other cases of failure too.

Regards,
  Anders