2 Made by Timothy Manning <timothy@yaffs.net> on 08/11/2010
6 Bug with opening a file with a name of 1,000,000 char long with no errors.
8 Bug with unlinking a file with 1,000,000 get the error ENOENT but should
9 be geting ENAMETOOLONG.
11 Bug with mounting a too long non-existant mount point is returning
12 ENODEV. there are two errors here, ENOENT and ENAMETOOLONG.
13 The ENODEV is the error which yaffs gives instead of ENOENT.
14 BBut the mount function should just return ENAMETOOLONG.
16 Bug when mounting a non-existing mount point. The error code returned is
19 Bug when trying to use yaffs_access on an existing file with mode 255
20 the error returned is EACCES it should be EINVAL(note there is no quick test file yet).
22 Bug when trying to access a non-existing directory the error ENOENT is
23 returned. It should be ENOTDIR.
25 Bug when trying to truncate a file in a non-existing directory. The error
26 returned is ENOENT it should be ENOTDIR.
28 Bug truncating a file to a size of -1 does not cause an error.
30 BUG truncating a file to a size greater than the maximum file size should
31 return the error EFBIG. However EFBIG has not been defined in yaffs and
32 needs to be added. When a file is truncated to a large size
33 (size =10000000000000000000000000000000000000000000) the truncate
34 function works without any errors, which is wrong.
36 Bug with opening a file with bad mode. yaffs_open has two modes which
37 are passed into it. if the modes are set to 255 the open function
38 does not report any errors. (Also need to try this with modes set to -1.)
42 WARNING- If yaffs is unmounted then most of yaffs' functions return ENODIR.
43 some function return EBADF instead.
45 WARNING- When mounting a non-existing mount point the error ENODEV is returned.
46 The quick tests have been altered to accommodate this error code.
47 With standard access function in linux the error returned is ENOENT.