mtd-utils.git/tests, branch v1.4.5

fs-tests: integck: add some more error messages

2011-05-27T12:55:08+00:00

Signed-off-by: Artem Bityutskiy

fs-tests: integck: print error message on error

2011-05-27T12:55:08+00:00

Currently pcv macro print the error message only if we are not doing power cut testing or if we have -v flag. But if we run without -v and an error happen and the error code is not EROFS/EIO, pcv() does not print anything. This patch makes it print the error message in that case as well. Signed-off-by: Artem Bityutskiy

fs-tests: integck: close files after creation

2011-05-27T12:55:08+00:00

The 'file_new()' function should create a file but should not keep it open. There is a different path to open files and keep them open. This patch makes 'file_new()' close newly created files. Signed-off-by: Artem Bityutskiy

fs-tests: integck: make directory checking work

2011-05-27T12:55:07+00:00

This patch makes the directory checking in case of power cut emulation actually work. There were many bugs. Basically, we cannot rely on anything unless the directory is marked as clean. Signed-off-by: Artem Bityutskiy

fs-tests: integck: add verbose reporting

2011-05-27T12:55:07+00:00

Make -v switch control verbose integck output. Signed-off-by: Artem Bityutskiy

fs-tests: integck: always check clean data

2011-05-27T12:55:07+00:00

Check the clean data after every emulated power cut, not only when 'create_test_data()'/'update_test_data()' succeed. This required some minor re-work. Signed-off-by: Artem Bityutskiy

fs-tests: integck: introduce a helper function for dir sync

2011-05-27T12:55:07+00:00

Add a helper 'sync_directory()' function to synchronize directories. Signed-off-by: Artem Bityutskiy

fs-tests: integck: print name of directory which we cannot open

2011-05-27T12:55:06+00:00

In 'dir_check()' print name of the directory if we fail to open it. Signed-off-by: Artem Bityutskiy

fs-tests: integck: EIO can also be return in power-cut testing

2011-05-27T12:55:06+00:00

Currently when we are doing UBIFS power cut emulation testing we assume that EROFS is returned in case of an emulated power cut event. However, this is not true and sometimes Linux returns EIO to user-space instead. Namely, this happens when we are waiting for write-back to finish. Here is a call trace form kernel 2.6.39-rc7: Call Trace: [] filemap_write_and_wait_range+0x78/0xb1 [] vfs_fsync_range+0x38/0xd3 [] generic_write_sync+0x43/0x65 [] generic_file_aio_write+0xaa/0xf2 [] ubifs_aio_write+0x13a/0x1a1 [ubifs] [] do_sync_write+0xcb/0x141 [] vfs_write+0xb0/0x150 [] sys_write+0x48/0x72 [] system_call_fastpath+0x16/0x1b 'filemap_fdatawait_range()' returns hard-coded -EIO if a page write-back happens with whatever error code. Thus, this patch teaches integck to handle EIO when doing power cut emulation testing. Signed-off-by: Artem Bityutskiy

fs-tests: integck: implement MTD reattaching

2011-05-27T12:55:06+00:00

This patch adds -m option to integck and teaches integck to re-attach the MTD device to UBI in case of an emulated power cut event. This is needed for the new UBI power cut and unstable bits emulation infrastructure: when UBI emulates a power cut the only way to recover form this is to re-attach the MTD device. Signed-off-by: Artem Bityutskiy