summaryrefslogtreecommitdiffstats
path: root/spec/build/testsuites/fstests
diff options
context:
space:
mode:
authorKinsey Moore <kinsey.moore@oarcorp.com>2024-01-16 10:32:55 -0600
committerJoel Sherrill <joel@rtems.org>2024-02-26 11:07:53 -0600
commite3972d71eff885599be5371d0f9c2744f7f3226d (patch)
tree5ba3a0bb0d890c17a29f300f7cd650f8e77538a6 /spec/build/testsuites/fstests
parentspec/zynqmp-rpu: Clean up options (diff)
downloadrtems-e3972d71eff885599be5371d0f9c2744f7f3226d.tar.bz2
cpukit/jffs2: Handle used empty file system
On JFFS2 file systems on NOR flash or dataflash that does not have spare area for metadata and thus does not invoke delayed writes, it is possible to put the file system into a state where all blocks have been written to and all files have been deleted from the filesystem. There is a bug in the JFFS2 file system scan routine that detects this situation as a corrupted file system since the scan routine relies on "used" space to discriminate a valid file system when there are blocks that need to be erased. The correct fix would require a partial rewrite of the scan routine, so instead this patch tracks the space marked as obsolete along with space at the end of each block that is otherwise too small to contain a JFFS2 node so that it can me compared with the dirty space. Corrupted data (or otherwise non-JFFS2 blocks) will still cause this check to fail as corrupted data isn't recognized as obsoleted (deleted) nodes.
Diffstat (limited to 'spec/build/testsuites/fstests')
0 files changed, 0 insertions, 0 deletions