February 14, 2021
f_mkfs function can create wrong exFAT volume.
This is a time dependent malfunction that two boot records each have different volumme sereal number. As the result, such exFAT volume cannot be mounted by Windows.
February 3, 2021
File gets dead-locked when f_open funciton failed with some conditions.
This is because the file is left locked when it is opened with FA_OPEN_APPEND flag and failed the
function due to a seek error.
November 10, 2019
Old floppy disks formatted with MS-DOS 2.x and 3.x cannot be mounted.
This is because the boot sector lacks "FAT" string and 0xAA55 signature.
August 30, 2019
Wrong memory read one or more characters beyond end of the input path name.
If the memory area following the string terminator is filled by / or \, it can cause memory
protection fault or bus fault.
February 14, 2019
f_readdir() function cannot retrieve long file names in length of FF_MAX_LFN - 1 characters.
f_open() function cannot find the file with file name in length of FF_MAX_LFN characters.
January 9, 2019
f_readdir() function returns file names with wrong case conversion.
When the directory item to be read has a file name within 8.3 format, the extension of file name
returned in fname[] is in wrong case conversion depends on the body length and the case.
Sep 3, 2018
f_getcwd function uses memory location beyond the output buffer length specified by argument if
the buffer has a valid drive number. It can collapse the data located next to the output buffer.
This problem was reported via email.
Jul 8, 2018
Creating a sub-directory in the fragmented sub-directory on the exFAT volume collapses FAT chain
of the parent directory. This problem was reported at the User Forum.
May 23, 2018
Reading a directory gets infinite loop.
Successive f_readdir() calls would not detect the end of directory if the directory was filled up
and the last entry is not empty. This problem was reported at the User Forum.
March 18, 2017
On the exFAT volume, NoFatChain flag of the file fragmented out of the
session is left not set after it gets contiguous again by f_truncate
function. Such a wrong contiguous file causes unreasonable performance
down at read/write operation of the file. (Appeared at R0.12)
March 9, 2015
At the thread-safe configuration (_FS_REENTRANT == 1), an unexpected
operation to the volume can result a wrong volume lock. For example,
f_open() ==> media change ==> f_close(), in this case the volume gets
left locked and following function calls to the volume will be locked
out until a forced initialization of the volume by f_mount(). To solve
this problem, apply this patch to the ff.c.
November 13, 2014
f_unlink function does not remove cluster chain of the file. It reads to
a lost cluster of the FAT volume. This is added at a bugfix of R0.10c.
Christopher Williams