JFFS2 wrong data CRC message

[David Woodhouse]

On Wed, 2007-05-02 at 15:51 +0200, Jörn Engel wrote:
> You could add a new node type to mark "safe" crc errors.  Something
> roughly like this:
> - Print error for crc errors, unless the next node in eraseblock is a
>   "known crc error" node.
> - Write "known crc error" node on mount for any node that is the last in
>   an eraseblock if there still is enough room to write further data.
> 
> That should be able to eliminate most false positive.  If you care.

I'm not sure we even need to go that far. If the data CRC fails and the
last data bytes are 0xFF rather than anything else, then it's almost
certain it's an unfinished write. I just don't care -- I'm happy enough
seeing the warning. 

-- 
dwmw2                       09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0