yaffs Have revised and checked each test in quick tests.

[yaffs2.git] / direct / timothy_tests / quick_tests / current_bugs.txt

diff --git a/direct/timothy_tests/quick_tests/current_bugs.txt b/direct/timothy_tests/quick_tests/current_bugs.txt
index 6435529689b0fb566db762a5b27f3237eeadae1f..ed659a14561e613b7c8ae10328f9c884c8f3dca3 100644 (file)
--- a/direct/timothy_tests/quick_tests/current_bugs.txt
+++ b/direct/timothy_tests/quick_tests/current_bugs.txt
@@ -30,6 +30,16 @@ Current BUGS
                Bug when trying to stat a file in a non-existing directory. The error 
                returned is ENOENT, it should be ENOTDIR 
 
+               Bug when trying to chmod a file in a non-existing directory. The error 
+               returned is ENOENT, it should be ENOTDIR 
+
+
+       
+       There may be a bug with trying to chmoding a file with the mode set to 0.
+       The chmod function does not return an error which means that it is unknown what modes the file is chmoded to.
+       When yaffs_open is used on the file the error EACCES is returned. It is possible that yaffs has changed the mode 
+       to read only.
+
        Bug with truncating to a very large size. The yaffs_truncate function truncates the file to a massive size without any errors.
        The function should return the error EINVAL. 
 
@@ -45,7 +55,7 @@ Current BUGS
        It should return EINVAL. This is because it was reading an empty file. 
        When text is added to the file a read of -1 bytes tries to read 4 gig of data 
 
-       Bug when writing a file. the writhing to the file causes the file size to exceed the size of yaffs file system memory.
+       Bug when writing a file. The writing to the file causes the file size to exceed the size of yaffs file system memory.
        Output of test:
                test_yaffs_write_EFBIG 
                AddrToChunk of offset -2147483648 gives chunk -1048576 start 0