mtd-utils.git/configure.ac, branch v2.3.1

Release mtd-utils-2.3.1

2026-04-13T07:07:48+00:00

Signed-off-by: David Oberhollenzer

mtd-utils: tests: jittertest: reject overlong file names

2026-04-13T06:42:56+00:00

plotJittervsFill copies the -f argument into a 250-byte buffer with strncpy(..., sizeof(LogFile)). A 250-byte file name leaves the buffer unterminated, and the subsequent fopen() reads past the end of LogFile. JitterTest uses the same fixed-size file name pattern for -r, while -c still silently truncates overlong names and -f already rejects them. Validate jittertest file name arguments before copying them so these options all reject overlong input instead of truncating it or reading past the end of fixed-size buffers. Add a shell regression test that exercises the accepted and rejected boundary lengths for plotJittervsFill and JitterTest during make check. Signed-off-by: Aviv Daum Signed-off-by: David Oberhollenzer

Release mtd-utils-2.3.0

2025-02-15T15:31:13+00:00

Signed-off-by: David Oberhollenzer

ubifs-utils: Support Address-Sanitizier debug

2024-11-11T09:32:46+00:00

Add new option '--asan' for configuration to support dynamic Address-Sanitizier debugging, which could detect kinds of invalid memory accessing problems(eg. UAF, r/w OOB, etc.). Currently, only ubifs-utils(mkfs.ubifs/fsck.ubifs) is supported. Enable Address-Sanitizier debugging with configuration: ./configure --enable-asan Notice: The Address-Sanitizier will stop the program and print problems if memory problems are detected. Sometimes the memory problems come from third libs(not mtd-utils), which could stuck the testcases. Signed-off-by: Zhihao Cheng Signed-off-by: David Oberhollenzer

tests: ubifs_tools: Add run_all script

2024-11-11T09:32:46+00:00

Add run_all script to run all UBIFS fsck & mkfs testcases. Signed-off-by: Zhihao Cheng Signed-off-by: David Oberhollenzer

tests: ubifs_tools: mkfs_tests: Add fs content check test

2024-11-11T09:32:46+00:00

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 Signed-off-by: David Oberhollenzer

tests: ubifs_tools: fsck_tests: Add bad images fixing test

2024-11-11T09:32:46+00:00

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 Signed-off-by: David Oberhollenzer

tests: ubifs_tools: fsck_tests: Add random_corrupt+fsck test

2024-11-11T09:32:46+00:00

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 Signed-off-by: David Oberhollenzer

tests: ubifs_tools: fsck_tests: Add cycle_powercut+fsck test

2024-11-11T09:32:46+00:00

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 Signed-off-by: David Oberhollenzer

tests: ubifs_tools: fsck_tests: Add corrupt+fsck+fault_inject test

2024-11-11T09:32:46+00:00

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 Signed-off-by: David Oberhollenzer