Made by Timothy Manning <timothy@yaffs.net> on 08/11/2010
-Current BUGS AND WARNINGS
- bug with opening a file with a name of 1,000,000 char long with no errors.
- 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. there are two errors here, ENOENT and ENAMETOOLONG.
- bug with mounting a non-existing mount point get the error ENODEV. should be getting ENOENT.
+Current BUGS
- bug when trying to use yaffs_access on an existing file with mode 255 the error returned is EACCES it should be EINVAL(note there is no quick test file yet).
- WARNING- If yaffs is unmounted then most functions return ENODIR.
+Current WARNINGS
+
+ WARNING- If yaffs is unmounted then most of yaffs' functions return ENODIR.
+ But some function return EBADF instead.
+ Functions which return ENOTDIR: open, close, access, unlink, lseek, write, read
+ Functions which return ENOENT: access, stat
+
+
+
+ WARNING-the function yaffs_open does not check the mode passed to it.
+ This means that yaffs open does not return EINVAL if a bad mode is passed to it.
+ However this causes the error EEXIST to happen instead, because both O_CREAT and O_EXCL flags are set.
+
+ WARNING- yaffs_open will work with either of the two mode set to 255.
+ However there are only 4 or 5 flags that can be set for each of the modes.
+ This means that the programmer may not be setting the flags properly.
+
+ WARNING- When mounting a non-existing mount point the error ENODEV is returned.
+ The quick tests have been altered to accommodate this error code.
+ With standard access function in linux the error returned is ENOENT.