Lines Matching refs:can
67 Fixed DBCS name can result FR_INVALID_NAME.
84 Fixed btr in f_read() can be mistruncated.
118 Fixed f_unlink() can return FR_OK on error.
195 Fixed f_write() can be truncated when the file size is close to 4GB.
196 Fixed f_open(), f_mkdir() and f_setlabel() can return incorrect value on error.
204 2nd argument of f_rename() can have a drive number and it will be ignored.
214 Fixed a hard error in the disk I/O layer can collapse the directory entry.
224 Fixed a potential problem of FAT access that can appear on disk error.
239 Fixed wrong media change can lead a deadlock at thread-safe configuration.
274 Fixed creating a file in the root directory of exFAT volume can fail. (appeared at R0.12)
275 …Fixed f_mkfs() creating exFAT volume with too small cluster size can collapse unallocated memory. …
276 Fixed wrong object name can be returned when read directory at Unicode cfg. (appeared at R0.12)
286 Fixed successive f_getfree() can return wrong count on the FAT12/16 volume. (appeared at R0.12)
300 …Fixed exFAT FAT entry can be collapsed when write or lseek operation to the existing file is done.…
301 …Fixed creating a file can fail when a new cluster allocation to the exFAT directory occures. (appe…
311 …Fixed f_unlink() can cause lost clusters at fragmented file on the exFAT volume. (appeared at R0.1…
320 …Fixed accesing any object on the exFAT root directory beyond the cluster boundary can fail. (appea…