On 05/02/2019 14:45, Tom Rini wrote:
On Mon, Feb 04, 2019 at 12:19:19PM +0100, Jean-Jacques Hiblot wrote:
We need to make sure that file writes,file creation, etc. are properly
performed and do not corrupt the filesystem.
To help with this, introduce the assert_fs_integrity() function that
executes the appropriate fsck tool. It should be called at the end of any
test that modifies the content/organization of the filesystem.
Currently only supports FATs and EXT4.
Signed-off-by: Jean-Jacques Hiblot <jjhib...@ti.com>
---
While working on symlink I had noticed the need for automated check of the
filesystem. It indeed helped catch a few corruption problems.
- SPOILER - this patch will turn some lights red in travis - SPOILER -
Oh fun. Do you have a link to the travis failures? Thanks!
Actually I was wrong. no red lights: the fs tests are skipped :/
Probably because they take so long to run.
I haven't figured out how they are disabled and how to enable them.
Nevertheless running the test at least on sandbox would be a pretty good
idea. It revealed some corruptions going on with FAT16 and FAT32
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
