mtd/fs/jffs3 TODO,3.3,3.4

[Artem Bityuckiy]

Update of /home/cvs/mtd/fs/jffs3
In directory phoenix.infradead.org:/tmp/cvs-serv16099

Modified Files:
	TODO 
Log Message:
Add one more TODO.


Index: TODO
===================================================================
RCS file: /home/cvs/mtd/fs/jffs3/TODO,v
retrieving revision 3.3
retrieving revision 3.4
diff -u -r3.3 -r3.4
--- TODO	16 Dec 2004 14:51:52 -0000	3.3
+++ TODO	17 Dec 2004 17:07:12 -0000	3.4
@@ -44,3 +44,12 @@
    - Consider changing the start seed to crc from 0 to -1. Zero
      is not a good start seed for crc
 
+   - Currently when JFFS3 founds any CRC error it prints warning message. This is right from one
+     hand. CRC errors may appear because of unclean reboots (1) and flash media corruptions (2).
+     Unclean reboots happen rather often and, as result, one node may have CRC error (JFFS2 was in
+     the middle of writing it when was rebooted uncleanly). Bu JFFS2 still prints CRC error warning.
+     That makes users worry. So, it is good to detect such situations and not to print the CRC error
+     warning message. Possibly, we may not print that if the bogus node is the last node in the current
+     block (may there be one more bogus node in the same block, if there were several consequent
+     unclean reboots? - not sure ...)
+