mtd-utils.git - A mirror of http://git.infradead.org/mtd-utils.git

Age	Commit message (Collapse)	Author
2024-11-11	tests: ubifs_tools: Add README	Zhihao Cheng
	Add document for fsck.ubifs and mkfs.ubifs testcases, explain all testcases and how to run them. Signed-off-by: Zhihao Cheng <chengzhihao1@huawei.com> Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star.at>
2024-11-11	tests: ubifs_tools: Add run_all script	Zhihao Cheng
	Add run_all script to run all UBIFS fsck & mkfs testcases. Signed-off-by: Zhihao Cheng <chengzhihao1@huawei.com> Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star.at>
2024-11-11	tests: ubifs_tools: mkfs_tests: Add fs content check test	Zhihao Cheng
	Initialize UBIFS image from a given directory, then check whether the fs content in mounted UBIFS is consistent with the original directory. Both UBI volume and file are chosen as storage mediums to test. Signed-off-by: Zhihao Cheng <chengzhihao1@huawei.com> Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star.at>
2024-11-11	tests: ubifs_tools: fsck_tests: Add bad images fixing test	Zhihao Cheng
	For kinds of inconsistent UBIFS images(which can simulate corruptions caused by some potentional UBIFS bug), check the result of fsck. This testcase mainly checks whether the behavior is in expected after repairing specific inconsistent UBIFS image. Signed-off-by: Zhihao Cheng <chengzhihao1@huawei.com> Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star.at>
2024-11-11	tests: ubifs_tools: fsck_tests: Add corrupted images	Zhihao Cheng
	This is a preparation for adding bad images fsck testcase. There is no debugfs tools (for example: debugfs[ext4], xfs_db) for UBIFS, so there is no way to inject precise corruption into UBIFS image, we have to prepare inconsistent UBIFS images in advance like e2fsprogs[1] does. (Goto [2] to see how to generate inconsistent UBIFS images). Original UBIFS image content: / ├── corrupt_file (xattr - user.corrupt:123, 2K data) ├── dir │ ├── block_dev │ ├── char_dev │ ├── dir │ └── file (content: '123') ├── hardl_corrupt_file => corrupt_file └── softl_corrupt_file -> corrupt_file Here's a descriptons of the various testing images: ========================================================================= image \| Description \| expectancy ------------------------------------------------------------------------- good \| good image contains \| fsck success, fs content is \| kinds of files. \| not changed. ------------------------------------------------------------------------- sb_fanout \| invalid fanout in \| fsck failed. \| superblock. \| ------------------------------------------------------------------------- sb_fmt_version \| invalid fmt_version \| fsck failed. \| in superblock. \| ------------------------------------------------------------------------- sb_leb_size \| invalid leb_size in \| fsck failed. \| superblock. \| ------------------------------------------------------------------------- sb_log_lebs \| invalid log lebs in \| fsck failed. \| superblock. \| ------------------------------------------------------------------------- sb_min_io_size \| invalid min_io_size \| fsck failed. \| in superblock. \| ------------------------------------------------------------------------- master_highest_inum \| invalid highest_inum\| fsck success, fs content is \| in master nodes. \| not changed. ------------------------------------------------------------------------- master_lpt \| bad lpt pos in \| fsck success, fs content is \| master nodes. \| not changed. ------------------------------------------------------------------------- master_tnc \| bad tnc pos in \| fsck success, fs content is \| master nodes. \| not changed. ------------------------------------------------------------------------- master_total_dead \| bad total_dead in \| fsck success, fs content is \| master nodes. \| not changed. ------------------------------------------------------------------------- master_total_dirty \| bad total_dirty in \| fsck success, fs content is \| master nodes. \| not changed. ------------------------------------------------------------------------- master_total_free \| bad total_free in \| fsck success, fs content is \| master nodes. \| not changed. ------------------------------------------------------------------------- journal_log \| corrupted log area. \| fsck success, fs content is \| \| not changed. ------------------------------------------------------------------------- journal_bud \| corrupted bud area. \| fsck success, file data is \| \| lost. ------------------------------------------------------------------------- orphan_node \| bad orphan node. \| fsck success, file is \| \| deleted as expected. ------------------------------------------------------------------------- lpt_dirty \| bad dirty in pnode. \| fsck success, fs content is \| \| not changed. ------------------------------------------------------------------------- lpt_flags \| bad flags in pnode \| fsck success, fs content is \| (eg. index). \| not changed. ------------------------------------------------------------------------- lpt_free \| bad free in pnode. \| fsck success, fs content is \| \| not changed. ------------------------------------------------------------------------- lpt_pos \| bad pos in nnode. \| fsck success, fs content is \| \| not changed. ------------------------------------------------------------------------- ltab_dirty \| bad dirty in lprops \| fsck success, fs content is \| table. \| not changed. ------------------------------------------------------------------------- ltab_free \| bad free in lprops \| fsck success, fs content is \| table. \| not changed. ------------------------------------------------------------------------- index_size \| bad index size in \| fsck success, fs content is \| master nodes. \| not changed. ------------------------------------------------------------------------- tnc_lv0_key \| bad key in lv0 \| fsck success, fs content is \| znode. \| not changed. ------------------------------------------------------------------------- tnc_lv0_len \| bad len in lv0 \| fsck success, fs content is \| znode. \| not changed. ------------------------------------------------------------------------- tnc_lv0_pos \| bad pos in lv0 \| fsck success, fs content is \| znode. \| not changed. ------------------------------------------------------------------------- tnc_noleaf_key \| bad key in non-leaf \| fsck success, fs content is \| znode. \| not changed. ------------------------------------------------------------------------- tnc_noleaf_len \| bad len in non-leaf \| fsck success, fs content is \| znode. \| not changed. ------------------------------------------------------------------------- tnc_noleaf_pos \| bad pos in non-leaf \| fsck success, fs content is \| znode. \| not changed. ------------------------------------------------------------------------- corrupted_data_leb \| corrupted data leb. \| fsck success, partial data of \| \| file is lost. ------------------------------------------------------------------------- corrupted_idx_leb \| corrupted index leb.\| fsck success, fs content is \| \| not changed. ------------------------------------------------------------------------- inode_data \| bad data node. \| fsck success, file content \| \| is changed, other files are \| \| not changed. ------------------------------------------------------------------------- inode_mode \| bad inode mode for \| fsck success, file is \| file. \| dropped, other files are not \| \| changed. ------------------------------------------------------------------------- inode_nlink \| wrong nlink for \| fsck success, nlink is \| file. \| corrected, fs content is not \| \| changed. ------------------------------------------------------------------------- inode_size \| wrong inode size \| fsck success, inode size is \| for file. \| corrected, fs content is not \| \| changed. ------------------------------------------------------------------------- inode_xcnt \| wrong inode \| fsck success, xattr_cnt is \| xattr_cnt for file. \| corrected, fs content is not \| \| changed. ------------------------------------------------------------------------- soft_link_inode_mode\| bad inode mode for \| fsck success, soft link \| solf link file. \| file is dropped, other files \| \| are not changed. ------------------------------------------------------------------------- soft_link_data_len \| bad inode data_len \| fsck success, soft link \| for solt link file. \| file is dropped, other files \| \| are not changed. ------------------------------------------------------------------------- dentry_key \| bad dentry key for \| fsck success, dentry is \| file. \| removed, other files are \| \| not changed. ------------------------------------------------------------------------- dentry_nlen \| inconsistent nlen \| fsck success, dentry is \| and name in dentry \| removed, other files are \| for file. \| not changed. ------------------------------------------------------------------------- dentry_type \| inconsistent type \| fsck success, dentry is \| between dentry and \| removed, other files are \| inode for file. \| not changed. ------------------------------------------------------------------------- xinode_flags \| lost UBIFS_XATTR_FL \| fsck success, xattr is \| in xattr inode \| removed, other files are \| flags for file. \| not changed. ------------------------------------------------------------------------- xinode_key \| bad xattr inode key \| fsck success, xattr is \| for file. \| removed, other files are \| \| not changed. ------------------------------------------------------------------------- xinode_mode \| bad xattr inode \| fsck success, xattr is \| mode for file. \| removed, other files are \| \| not changed. ------------------------------------------------------------------------- xentry_key \| bad xattr entry key \| fsck success, xattr is \| for file. \| removed, other files are \| \| not changed. ------------------------------------------------------------------------- xentry_nlen \| inconsistent nlen \| fsck success, xattr is \| and name in xattr \| removed, other files are \| entry for file. \| not changed. ------------------------------------------------------------------------- xentry_type \| inconsistent type \| fsck success, xattr is \| between xattr entry \| removed, other files are \| and xattr inode for \| not changed. \| file. \| ------------------------------------------------------------------------- xent_host \| the xattr's host \| fsck success, file, hard \| is a xattr too, the \| link and soft link are \| flag of corrupt_file\| dropped, other files are \| inode is modified. \| not changed. ------------------------------------------------------------------------- dir_many_dentry \| dir has too many \| fsck success, hard link is \| dentries, the dentry\| dropped, other files are not \| of hard link is \| changed. \| modified. \| ------------------------------------------------------------------------- dir_lost \| bad dentry for dir. \| fsck success, the 'file' is \| \| recovered under lost+found, \| \| left files under dir are \| \| removed, other files are not \| \| changed. ------------------------------------------------------------------------- dir_lost_duplicated \| bad inode for dir, \| fsck success, the 'file' is \| there is a file \| recovered with INO_<inum>_1 \| under lost+found, \| under lost+found, left files \| which named with the\| under dir are removed, other \| inum of the 'file'. \| files are not changed. ------------------------------------------------------------------------- dir_lost_not_recover\| bad inode for dir, \| fsck success, all files \| lost+found is a \| under dir are removed, \| regular file and \| other files are not changed. \| exists under root \| \| dir. \| ------------------------------------------------------------------------- root_dir \| bad '/'. \| fsck success, create new \| \| root dir('/'). All regular \| \| files are reocovered under \| \| lost+found, other files are \| \| removed. ------------------------------------------------------------------------- empty_tnc \| all files have bad \| fsck success, fs content \| inode. \| becomes empty. ========================================================================= [1] https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/tree/tests/README [2] https://bugzilla.kernel.org/show_bug.cgi?id=218924 Signed-off-by: Zhihao Cheng <chengzhihao1@huawei.com> Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star.at>
2024-11-11	tests: ubifs_tools: fsck_tests: Add random_corrupt+fsck test	Zhihao Cheng
	Inject random corruption on UBIFS image by writting random data on kinds of mtd devices (eg. nand, nor), check the consistency of UBIFS after fsck. This testcase simulates random bad UBIFS image caused by hardware exceptions(eg. ecc uncorrectable, unwritten), and makes sure that fsck.ubifs could make UBIFS be consistent after repairing UBIFS image. Signed-off-by: Zhihao Cheng <chengzhihao1@huawei.com> Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star.at>
2024-11-11	tests: ubifs_tools: fsck_tests: Add cycle_powercut+fsck test	Zhihao Cheng
	Inject powercut while doing fsstress on mounted UBIFS, check the consistency of UBIFS after fsck. This testscase mainly makes sure that fsck.ubifs can make UBIFS image be consistent in common stress cases and powercut cases. Signed-off-by: Zhihao Cheng <chengzhihao1@huawei.com> Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star.at>
2024-11-11	tests: ubifs_tools: fsck_tests: Add corrupt+fsck+fault_inject test	Zhihao Cheng
	Inject memory/io fault while doing fsck for corrupted UBIFS images. This testcase mainly checks whether fsck.ubifs has problems (eg. UAF, null-ptr-def, etc.) in random error paths. Besides, it provides a similar way to simulate powercut during fsck, and checks whether the fsck.ubifs can fix an UBIFS image after many rounds interrupted by kinds of errors. Signed-off-by: Zhihao Cheng <chengzhihao1@huawei.com> Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star.at>
2024-11-11	tests: ubifs_tools: fsck_tests: Add powercut+fsck+mount test	Zhihao Cheng
	Inject powercut while doing fsstress on mounted UBIFS for kinds of flashes (eg. nand, nor). This testcase mainly makes sure that fsck.ubifs can make UBIFS image be consistent on different flashes (eg. nand, nor). Because the min_io_size of nor flash is 1, the UBIFS image on nor flash will be different from nand flash after doing powercut, so we need make sure fsck.ubifs can handle these two types of flash. Signed-off-by: Zhihao Cheng <chengzhihao1@huawei.com> Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star.at>
2024-11-11	tests: ubifs_tools: fsck_tests: Add cycle mount+fsck test	Zhihao Cheng
	Do fsstress and fsck, check whether there are any files(and their data) are lost after fsck. This testcase mainly checks whether fsck.ubifs could corrupt the filesystem content in common case. Signed-off-by: Zhihao Cheng <chengzhihao1@huawei.com> Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star.at>
2024-11-11	tests: ubifs_tools: fsck_tests: Add authentication refusing test	Zhihao Cheng
	Authenticated UBIFS image is not supported in fsck, add testcase to check that. Signed-off-by: Zhihao Cheng <chengzhihao1@huawei.com> Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star.at>
2024-11-11	tests: Add common libs for testing fsck.ubifs/mkfs.ubifs	Zhihao Cheng
	This is a preparation for adding testcases for fsck.ubifs and mkfs.ubifs. Add some common functions, for example: powercut, load_mtdram, mount_ubifs, encryption operations, etc. Signed-off-by: Zhihao Cheng <chengzhihao1@huawei.com> Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star.at>