X-Git-Url: http://www.aleph1.co.uk/gitweb/?p=yaffs2.git;a=blobdiff_plain;f=direct%2Ftimothy_tests%2Fquick_tests%2Fcurrent_bugs.txt;h=17c52f38edcdaaa0e1f31b1ab6415cf0f3555572;hp=b46434fdbaadc985a63c71f8b83b09d0101e5b11;hb=d3abc5c5da005343e7d78c5c9a51d58af14b3faa;hpb=24f00634ca4584100b60d7b68675c1c9c4646ee8 diff --git a/direct/timothy_tests/quick_tests/current_bugs.txt b/direct/timothy_tests/quick_tests/current_bugs.txt index b46434f..17c52f3 100644 --- a/direct/timothy_tests/quick_tests/current_bugs.txt +++ b/direct/timothy_tests/quick_tests/current_bugs.txt @@ -4,67 +4,14 @@ Made by Timothy Manning on 08/11/2010 Current BUGS - NAME SIZE - Bug with opening a file with a name of 1,000,000 char long with no errors. - The open function should be returning ENAMETOOLONG. + BUG with trying to rmdir /yaffs2/ the error returned is ENOTEMPTY. + But the error that should be returned is EBUSY. - Bug with unlinking a file with 1,000,000 get the error ENOENT but should - be geting ENAMETOOLONG. - - Bug with mounting a too long non-existant mount point is returning - ENODEV. yaffs_mount should be returning ENAMETOOLONG. - When the name is passed into the yaffs_mount function the length of the - mount point decreases from around 10000000 to 200. This needs to be investigated. - - Bug with unmounting a too long non-existing mountpoint. - The error returned is ENODEV. It should be ENAMETOOLONG. - - - ENOTDIR ERRORS - Bug when trying to access a non-existing directory the error ENOENT is - returned. It should be ENOTDIR. - - Bug when trying to truncate a file in a non-existing directory. The error - returned is ENOENT it should be ENOTDIR. - - 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 - - Bug when trying to mkdir on top of a non-existing directory. The error - returned is ENOENT, it should be ENOTDIR. yaffs_mkdir should never return ENOENT. - - - 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. - - Bug with lseeking to a very large size (size =100000000000000000000000000000000000000) without causing an error. - Should cause the error EINVAL. - - Bug with unmounting a non-existing mountpoint. The function returns ENODEV - but should be returning EINVAL. - - - 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_big_file - AddrToChunk of offset -2147483648 gives chunk -1048576 start 0 - AddrToChunk of offset -2147481600 gives chunk -1048575 start 0 - AddrToChunk of offset -2147479552 gives chunk -1048574 start 0 - AddrToChunk of offset -2147477504 gives chunk -1048573 start 0 - AddrToChunk of offset -2147475456 gives chunk -1048572 start 0 - AddrToChunk of offset -2147473408 gives chunk -1048571 start 0 - AddrToChunk of offset -2147471360 gives chunk -1048570 start 0 - AddrToChunk of offset -2147469312 gives chunk -1048569 start 0 - AddrToChunk of offset -2147467264 gives chunk -1048568 start 0 - AddrToChunk of offset -2147465216 gives chunk -1048567 start 0 - wrote a large amount of text to a file.(which is a bad thing) - test: test_yaffs_write_big_file failed - yaffs_error code 0 - error is : Unknown error code + BUG with trying to rmdir /yaffs2/. the error returned is ENOENT. + But the error that should be returned is EINVAL. + BUG with having slashes on the end of the second path passed into the rename function. + The function returns ENOENT. but should be returning other errors. Current WARNINGS