| commit | fa77a1b5a36347d95e230807195b76e3d2ee2743 | |
| author | Qu Wenruo <quwenruo@cn.fujitsu.com> | |
| Tue, 21 Feb 2017 08:34:33 +0000 (21 16:34 +0800) | ||
| committer | David Sterba <dsterba@suse.com> | |
| Wed, 8 Mar 2017 12:00:49 +0000 (8 13:00 +0100) | ||
| tree | 9a1822de482e7068f48ac2288c625cfeb1f2d0b2 | treesnapshot (tar.gz zip) |
| parent | 3aed1a1ced3b1d45c83abc34d32677edc7cd422f | commitdiff |
btrfs-progs: tests: Move fsck-tests/015 to fuzz tests
The test case fsck-tests/015-check-bad-memory-access can't be repair by
btrfs check, and it's a fortunate bug makes original mode to forget the
error code from extent tree, making original mode pass it.
So fuzz-tests is more suitable for it.
Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
Signed-off-by: David Sterba <dsterba@suse.com>
The test case fsck-tests/015-check-bad-memory-access can't be repair by
btrfs check, and it's a fortunate bug makes original mode to forget the
error code from extent tree, making original mode pass it.
So fuzz-tests is more suitable for it.
Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
Signed-off-by: David Sterba <dsterba@suse.com>
| tests/fuzz-tests/images/bko-97171-btrfs-image.raw.txt | [moved from tests/fsck-tests/015-check-bad-memory-access/bko-97171-btrfs-image.raw.txt with 100% similarity] | blobblamehistory |
| tests/fuzz-tests/images/bko-97171-btrfs-image.raw.xz | [moved from tests/fsck-tests/015-check-bad-memory-access/bko-97171-btrfs-image.raw.xz with 100% similarity] | blobblamehistory |