| Message ID | 20170221083438.25719-8-quwenruo@cn.fujitsu.com (mailing list archive) |
|---|---|
| State | Accepted |
| Headers | show |
diff --git a/tests/fsck-tests/015-check-bad-memory-access/bko-97171-btrfs-image.raw.txt b/tests/fuzz-tests/images/bko-97171-btrfs-image.raw.txt similarity index 100% rename from tests/fsck-tests/015-check-bad-memory-access/bko-97171-btrfs-image.raw.txt rename to tests/fuzz-tests/images/bko-97171-btrfs-image.raw.txt diff --git a/tests/fsck-tests/015-check-bad-memory-access/bko-97171-btrfs-image.raw.xz b/tests/fuzz-tests/images/bko-97171-btrfs-image.raw.xz similarity index 100% rename from tests/fsck-tests/015-check-bad-memory-access/bko-97171-btrfs-image.raw.xz rename to tests/fuzz-tests/images/bko-97171-btrfs-image.raw.xz
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> --- .../images}/bko-97171-btrfs-image.raw.txt | 0 .../images}/bko-97171-btrfs-image.raw.xz | Bin 2 files changed, 0 insertions(+), 0 deletions(-) rename tests/{fsck-tests/015-check-bad-memory-access => fuzz-tests/images}/bko-97171-btrfs-image.raw.txt (100%) rename tests/{fsck-tests/015-check-bad-memory-access => fuzz-tests/images}/bko-97171-btrfs-image.raw.xz (100%)