ext4: Add a test for rename with RENAME_WHITEOUT
PATCH v2 1/1 ext4: Add a test for rename with RENAME_WHITEOUT
Fill the disk space, try to create some files and rename a file, mount again, list directory contents and triggers some errors. It is a regression test for kernel commit 6b4b8e6b4ad8 ("ext4: ext4: fix bug for rename with RENAME_WHITEOUT")
---
v1 -> v3:
Use the original in src and modify 048.out
---
--- tests/ext4/048 | 76 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ tests/ext4/048.out | 2 ++ tests/ext4/group | 1 + 3 files changed, 79 insertions(+) create mode 100755 tests/ext4/048 create mode 100644 tests/ext4/048.out
tests/ext4/048 new file +76 -0
@@ -0,0 +1,76 @@ +#! /bin/bash +# SPDX-License-Identifier: GPL-2.0 +# Copyright (c) 2021 HUAWEI. All Rights Reserved. +# +# FS QA Test 048 +# +# This is a regression test for kernel patch: +# commit 6b4b8e6b4ad8 ("ext4: ext4: fix bug for rename with RENAME_WHITEOUT") + +seq=`basename $0` +seqres=$RESULT_DIR/$seq +echo "QA output created by $seq" + +here=`pwd` +tmp=/tmp/$$ +status=1 # failure is the default! +trap "_cleanup; exit \$status" 0 1 2 3 15 + +_cleanup() +{ + cd / + rm -f $tmp.* +} + +# get standard environment, filters and checks +. ./common/rc +. ./common/filter + +# remove previous $seqres.full before test +rm -f $seqres.full + +# real QA test starts here + +# Modify as appropriate. +_supported_fs ext4 +_supported_fs generic +_require_scratch +_require_xfs_io_command "falloc" + +dmesg -c > /dev/null + +_scratch_mkfs > $seqres.full 2>&1 +_scratch_mount >> $seqres.full 2>&1 + +testdir=$SCRATCH_MNT +cd ${testdir} + +mkdir test +$XFS_IO_PROG -f -c "falloc 0 128M" img >> $seqres.full +$MKFS_EXT4_PROG img > /dev/null 2>&1 +$MOUNT_PROG img test + +# fill the disk space +dd if=/dev/zero of=test/foo bs=1M count=128 > /dev/null 2>&1 + +# create 1000 files, not all the files will be created successfully +mkdir test/dir +cd test/dir +for ((i = 0; i < 1000; i++)) +do + touch file$i > /dev/null 2>&1 +done + +# try to rename, but now no space left on device +$here/src/renameat2 -w $testdir/test/dir/file1 $testdir/test/dir/dst_file + +cd $testdir +$UMOUNT_PROG test +$MOUNT_PROG img test +ls -l test/dir/file1 > /dev/null 2>&1 +$UMOUNT_PROG test + +dmesg -c | grep "deleted inode referenced" +# success, all done +status=0 +exit
tests/ext4/048.out new file +2 -0
@@ -0,0 +1,2 @@ +QA output created by 048 +No space left on device
tests/ext4/group +1 -0
@@ -50,6 +50,7 @@ 045 auto dir 046 auto prealloc quick 047 auto quick dax +048 other 271 auto rw quick 301 aio auto ioctl rw stress defrag 302 aio auto ioctl rw stress defrag
Signature · 1 line
2.13.6
Quoted 50 lines · Sun Ke
Fill the disk space, try to create some files and rename a file, mount again, list directory contents and triggers some errors. It is a regression test for kernel commit
6b4b8e6b4ad8("ext4: ext4: fix bug for rename withRENAME_WHITEOUT")Signed-off-by Sun Ke <[email protected]>---
v1 -> v3:
Use the original in src and modify 048.out
------ tests/ext4/048 | 76 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ tests/ext4/048.out | 2 ++ tests/ext4/group | 1 + 3 files changed, 79 insertions(+) create mode 100755 tests/ext4/048 create mode 100644 tests/ext4/048.outtests/ext4/048 new file +26
-0@@ -0,0 +1,76 @@ +#! /bin/bash +# SPDX-License-Identifier: GPL-2.0 +# Copyright (c) 2021 HUAWEI. All Rights Reserved. +# +# FS QA Test 048 +# +# This is a regression test for kernel patch: +# commit 6b4b8e6b4ad8 ("ext4: ext4: fix bug for rename with RENAME_WHITEOUT") + +seq=`basename $0` +seqres=$RESULT_DIR/$seq +echo "QA output created by $seq" + +here=`pwd` +tmp=/tmp/$$ +status=1 # failure is the default! +trap "_cleanup; exit \$status" 0 1 2 3 15 + +_cleanup() +{ + cd / + rm -f $tmp.* +} + +# get standard environment, filters and checks +. ./common/rc
tests/ext4/048 line 36
Quoted 10 lines
tests/ext4/048 new file +10
-0+. ./common/filter + +# remove previous $seqres.full before test +rm -f $seqres.full + +# real QA test starts here + +# Modify as appropriate. +_supported_fs ext4 +_supported_fs generic
ext4 or generic? Tell the truth, according to below testing steps, I think it can be a generic test case, not only for ext4.
Quoted 5 lines
tests/ext4/048 new file +5
-0+_require_scratch +_require_xfs_io_command "falloc" + +dmesg -c > /dev/null +
tests/ext4/048 line 51
Quoted 10 lines
tests/ext4/048 new file +10
-0+_scratch_mkfs > $seqres.full 2>&1 +_scratch_mount >> $seqres.full 2>&1 + +testdir=$SCRATCH_MNT +cd ${testdir} + +mkdir test +$XFS_IO_PROG -f -c "falloc 0 128M" img >> $seqres.full +$MKFS_EXT4_PROG img > /dev/null 2>&1 +$MOUNT_PROG img test
Can we reproduce this bug by $SCRATCH_DEV directly, not through a loopdev. Likes:
_scratch_mkfs_sized 128M (maybe bigger ?)_scratch_mount
tests/ext4/048 line 54
Quoted 3 lines
tests/ext4/048 new file +3
-0+ +# fill the disk space +dd if=/dev/zero of=test/foo bs=1M count=128 > /dev/null 2>&1
Can _fill_fs() helper help you that?
tests/ext4/048 line 62
Quoted 8 lines
tests/ext4/048 new file +8
-0+ +# create 1000 files, not all the files will be created successfully +mkdir test/dir +cd test/dir +for ((i = 0; i < 1000; i++)) +do + touch file$i > /dev/null 2>&1 +done
I don't know if it can be 100% sure there's at least 1 file will be created at here, after you tried to fill the fs.
So I think maybe you can create a file with known name, then use _fill_fs() to fill the whole fs. Then try to rename the file you know its name. Can that reproduce the bug?
tests/ext4/048 line 73
Quoted 11 lines
tests/ext4/048 new file +11
-0+ +# try to rename, but now no space left on device +$here/src/renameat2 -w $testdir/test/dir/file1 $testdir/test/dir/dst_file + +cd $testdir +$UMOUNT_PROG test +$MOUNT_PROG img test +ls -l test/dir/file1 > /dev/null 2>&1 +$UMOUNT_PROG test + +dmesg -c | grep "deleted inode referenced"
Can _check_dmesg_for() help you?
Quoted 16 lines
tests/ext4/048 new file +3
-0+# success, all done +status=0 +exittests/ext4/048.out new file +2
-0@@ -0,0 +1,2 @@ +QA output created by 048 +No space left on devicetests/ext4/group +0
-0
tests/ext4/group line 53
Quoted 4 lines
tests/ext4/group +1
-0@@ -50,6 +50,7 @@ 045 auto dir 046 auto prealloc quick 047 auto quick dax +048 other
I think your test case is a general test case, "auto"and "rename" groups are good to it, if it's quick enough, add "quick" group.
Quoted 6 lines
tests/ext4/group +0
-0271 auto rw quick 301 aio auto ioctl rw stress defrag 302 aio auto ioctl rw stress defragSignature · 1 line
2.13.6
hi, Zorro
Quoted 55 lines · Zorro Lang
Quoted 54 lines · Sun Ke
Fill the disk space, try to create some files and rename a file, mount again, list directory contents and triggers some errors. It is a regression test for kernel commit
6b4b8e6b4ad8("ext4: ext4: fix bug for rename withRENAME_WHITEOUT")Signed-off-by Sun Ke <[email protected]>---
v1 -> v3:
Use the original in src and modify 048.out
------ tests/ext4/048 | 76 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ tests/ext4/048.out | 2 ++ tests/ext4/group | 1 + 3 files changed, 79 insertions(+)create mode 100755 tests/ext4/048
create mode 100644 tests/ext4/048.outtests/ext4/048 new file +30
-0@@ -0,0 +1,76 @@ +#! /bin/bash +# SPDX-License-Identifier: GPL-2.0 +# Copyright (c) 2021 HUAWEI. All Rights Reserved. +# +# FS QA Test 048 +# +# This is a regression test for kernel patch: +# commit 6b4b8e6b4ad8 ("ext4: ext4: fix bug for rename with RENAME_WHITEOUT") + +seq=`basename $0` +seqres=$RESULT_DIR/$seq +echo "QA output created by $seq" + +here=`pwd` +tmp=/tmp/$$ +status=1 # failure is the default! +trap "_cleanup; exit \$status" 0 1 2 3 15 + +_cleanup() +{ + cd / + rm -f $tmp.* +} + +# get standard environment, filters and checks +. ./common/rc +. ./common/filter + +# remove previous $seqres.full before test +rm -f $seqres.full
Quoted 8 lines
tests/ext4/048 line 36
Quoted 6 lines
tests/ext4/048 new file +6
-0+ +# real QA test starts here + +# Modify as appropriate. +_supported_fs ext4 +_supported_fs genericext4 or generic? Tell the truth, according to below testing steps, I think it can be a generic test case, not only for ext4.
When reproducing the bug, demsg show :
EXT4-fs error (device loop0): ext4_lookup:1440: inode #2049: comm ls: deleted inode referenced: 139
It was printed in fs/ext4/super.c in funcation __ext4_error_inode. I search "deleted inode referenced" in linux kernel
and find 4 places:
fs/ext2/namei.c: "deleted inode referenced: %lu",
fs/ext4/namei.c: "deleted inode referenced: %u",
fs/minix/inode.c: printk("MINIX-fs: deleted inode referenced: %lu\n", fs/minix/inode.c: printk("MINIX-fs: deleted inode referenced: %lu\n",
If it is generic, I am not very sure how to distinguish success from failure.
Quoted 37 lines
Quoted 5 lines
tests/ext4/048 new file +5
-0+_require_scratch +_require_xfs_io_command "falloc" + +dmesg -c > /dev/null +tests/ext4/048 line 51
Quoted 10 lines
tests/ext4/048 new file +10
-0+_scratch_mkfs > $seqres.full 2>&1 +_scratch_mount >> $seqres.full 2>&1 + +testdir=$SCRATCH_MNT +cd ${testdir} + +mkdir test +$XFS_IO_PROG -f -c "falloc 0 128M" img >> $seqres.full +$MKFS_EXT4_PROG img > /dev/null 2>&1 +$MOUNT_PROG img testCan we reproduce this bug by $SCRATCH_DEV directly, not through a loopdev. Likes:
_scratch_mkfs_sized128M (maybe bigger ?)_scratch_mounttests/ext4/048 line 54
Quoted 3 lines
tests/ext4/048 new file +3
-0+ +# fill the disk space +dd if=/dev/zero of=test/foo bs=1M count=128 > /dev/null 2>&1Can
_fill_fs()helper help you that?tests/ext4/048 line 62
Quoted 8 lines
tests/ext4/048 new file +8
-0+ +# create 1000 files, not all the files will be created successfully +mkdir test/dir +cd test/dir +for ((i = 0; i < 1000; i++)) +do + touch file$i > /dev/null 2>&1 +doneI don't know if it can be 100% sure there's at least 1 file will be created at here, after you tried to fill the fs.
Quoted 3 lines
So I think maybe you can create a file with known name, then use
_fill_fs()to fill the whole fs. Then try to rename the file you know its name. Can that reproduce the bug?
OK, I am not sure, let me have a try.
Quoted 28 lines
tests/ext4/048 line 73
Quoted 12 lines
tests/ext4/048 new file +11
-0+ +# try to rename, but now no space left on device +$here/src/renameat2 -w $testdir/test/dir/file1 $testdir/test/dir/dst_file + +cd $testdir +$UMOUNT_PROG test +$MOUNT_PROG img test +ls -l test/dir/file1 > /dev/null 2>&1 +$UMOUNT_PROG test + +dmesg -c | grep "deleted inode referenced"Can
_check_dmesg_for()help you?Quoted 14 lines
tests/ext4/048 new file +3
-0+# success, all done +status=0 +exittests/ext4/048.out new file +2
-0@@ -0,0 +1,2 @@ +QA output created by 048 +No space left on devicetests/ext4/group +0
-1--- a/tests/ext4/group
Quoted 8 lines
tests/ext4/group line 53
Quoted 6 lines
+++ b/tests/ext4/group
tests/ext4/group +1
-0@@ -50,6 +50,7 @@ 045 auto dir 046 auto prealloc quick 047 auto quick dax +048 otherI think your test case is a general test case, "auto"and "rename" groups are good to it, if it's quick enough, add "quick" group.
Thanks for your suggestion.
Thanks,
Sun Ke
Quoted 8 lines
Quoted 7 lines
tests/ext4/group +0
-0271 auto rw quick 301 aio auto ioctl rw stress defrag 302 aio auto ioctl rw stress defragSignature · 1 line
2.13.6.
Quoted 84 lines · Sun Ke
hi, Zorro
Quoted 55 lines · Zorro Lang
Quoted 54 lines · Sun Ke
Fill the disk space, try to create some files and rename a file, mount again, list directory contents and triggers some errors. It is a regression test for kernel commit
6b4b8e6b4ad8("ext4: ext4: fix bug for rename withRENAME_WHITEOUT")Signed-off-by Sun Ke <[email protected]>---
v1 -> v3:
Use the original in src and modify 048.out
------ tests/ext4/048 | 76 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ tests/ext4/048.out | 2 ++ tests/ext4/group | 1 + 3 files changed, 79 insertions(+)create mode 100755 tests/ext4/048
create mode 100644 tests/ext4/048.outtests/ext4/048 new file +30
-0@@ -0,0 +1,76 @@ +#! /bin/bash +# SPDX-License-Identifier: GPL-2.0 +# Copyright (c) 2021 HUAWEI. All Rights Reserved. +# +# FS QA Test 048 +# +# This is a regression test for kernel patch: +# commit 6b4b8e6b4ad8 ("ext4: ext4: fix bug for rename with RENAME_WHITEOUT") + +seq=`basename $0` +seqres=$RESULT_DIR/$seq +echo "QA output created by $seq" + +here=`pwd` +tmp=/tmp/$$ +status=1 # failure is the default! +trap "_cleanup; exit \$status" 0 1 2 3 15 + +_cleanup() +{ + cd / + rm -f $tmp.* +} + +# get standard environment, filters and checks +. ./common/rc +. ./common/filter + +# remove previous $seqres.full before test +rm -f $seqres.fullQuoted 8 lines
tests/ext4/048 line 36
Quoted 6 lines
tests/ext4/048 new file +6
-0+ +# real QA test starts here + +# Modify as appropriate. +_supported_fs ext4 +_supported_fs genericext4 or generic? Tell the truth, according to below testing steps, I think it can be a generic test case, not only for ext4.
When reproducing the bug, demsg show :
EXT4-fs error (device loop0): ext4_lookup:1440: inode #2049: comm ls:
deleted inode referenced: 139It was printed in
fs/ext4/super.cin funcation__ext4_error_inode. I search "deleted inode referenced" in linux kerneland find 4 places:
fs/ext2/namei.c: "deleted inode referenced: %lu",fs/ext4/namei.c: "deleted inode referenced: %u", fs/minix/inode.c: printk("MINIX-fs: deleted inode
referenced: %lu\n",
fs/minix/inode.c: printk("MINIX-fs: deleted inode
referenced: %lu\n",
Quoted 2 lines
If it is generic, I am not very sure how to distinguish success from failure.
Except this dmesg check, all other steps aren't extN related. So I'd like to recommand:
1) Checking if we have a better way to avoid checking this ext4 only dmesg output? Likes if that "ls -l test/dir/file1" can find this bug? Does it have different output with/without the bug fix?
2) If we can't do the 1), and must check the ext4-only dmesg, we can use a judgement to check it for extN only:
if [[ $FSTYP =~ ext ]];then
check that dmesg
fi
then let other filesystems do dmesg checking by default.
But the 1) is still the best way I think.
Thanks,
Zorro
Quoted 96 lines
Quoted 39 lines
Quoted 7 lines
tests/ext4/048 new file +5
-0+_require_scratch +_require_xfs_io_command "falloc" + +dmesg -c > /dev/null +tests/ext4/048 line 51
Quoted 10 lines
tests/ext4/048 new file +10
-0+_scratch_mkfs > $seqres.full 2>&1 +_scratch_mount >> $seqres.full 2>&1 + +testdir=$SCRATCH_MNT +cd ${testdir} + +mkdir test +$XFS_IO_PROG -f -c "falloc 0 128M" img >> $seqres.full +$MKFS_EXT4_PROG img > /dev/null 2>&1 +$MOUNT_PROG img testCan we reproduce this bug by $SCRATCH_DEV directly, not through a loopdev. Likes:
_scratch_mkfs_sized128M (maybe bigger ?)_scratch_mounttests/ext4/048 line 54
Quoted 3 lines
tests/ext4/048 new file +3
-0+ +# fill the disk space +dd if=/dev/zero of=test/foo bs=1M count=128 > /dev/null 2>&1Can
_fill_fs()helper help you that?tests/ext4/048 line 62
Quoted 8 lines
tests/ext4/048 new file +8
-0+ +# create 1000 files, not all the files will be created successfully +mkdir test/dir +cd test/dir +for ((i = 0; i < 1000; i++)) +do + touch file$i > /dev/null 2>&1 +doneI don't know if it can be 100% sure there's at least 1 file will be created at here, after you tried to fill the fs.
Quoted 3 lines
So I think maybe you can create a file with known name, then use
_fill_fs()to fill the whole fs. Then try to rename the file you know its name. Can that reproduce the bug?OK, I am not sure, let me have a try.
Quoted 28 lines
tests/ext4/048 line 73
Quoted 12 lines
tests/ext4/048 new file +11
-0+ +# try to rename, but now no space left on device +$here/src/renameat2 -w $testdir/test/dir/file1 $testdir/test/dir/dst_file + +cd $testdir +$UMOUNT_PROG test +$MOUNT_PROG img test +ls -l test/dir/file1 > /dev/null 2>&1 +$UMOUNT_PROG test + +dmesg -c | grep "deleted inode referenced"Can
_check_dmesg_for()help you?Quoted 14 lines
tests/ext4/048 new file +3
-0+# success, all done +status=0 +exittests/ext4/048.out new file +2
-0@@ -0,0 +1,2 @@ +QA output created by 048 +No space left on devicetests/ext4/group +0
-1--- a/tests/ext4/groupQuoted 8 lines
tests/ext4/group line 53
Quoted 6 lines
+++ b/tests/ext4/group
tests/ext4/group +1
-0@@ -50,6 +50,7 @@ 045 auto dir 046 auto prealloc quick 047 auto quick dax +048 otherI think your test case is a general test case, "auto"and "rename" groups are good to it, if it's quick enough, add "quick" group.
Thanks for your suggestion.
Thanks,
Sun Ke
Quoted 8 lines
Quoted 7 lines
tests/ext4/group +0
-0271 auto rw quick 301 aio auto ioctl rw stress defrag 302 aio auto ioctl rw stress defragSignature · 1 line
2.13.6.
Hi, Zorro
Quoted 82 lines · Zorro Lang
Quoted 50 lines · Sun Ke
Fill the disk space, try to create some files and rename a file, mount again, list directory contents and triggers some errors. It is a regression test for kernel commit
6b4b8e6b4ad8("ext4: ext4: fix bug for rename withRENAME_WHITEOUT")Signed-off-by Sun Ke <[email protected]>---
v1 -> v3:
Use the original in src and modify 048.out
------ tests/ext4/048 | 76 ++++++++++++++++++++++++++++++++++++++++++++++++++++++ tests/ext4/048.out | 2 ++ tests/ext4/group | 1 + 3 files changed, 79 insertions(+)create mode 100755 tests/ext4/048
create mode 100644 tests/ext4/048.outtests/ext4/048 new file +26
-0@@ -0,0 +1,76 @@ +#! /bin/bash +# SPDX-License-Identifier: GPL-2.0 +# Copyright (c) 2021 HUAWEI. All Rights Reserved. +# +# FS QA Test 048 +# +# This is a regression test for kernel patch: +# commit 6b4b8e6b4ad8 ("ext4: ext4: fix bug for rename with RENAME_WHITEOUT") + +seq=`basename $0` +seqres=$RESULT_DIR/$seq +echo "QA output created by $seq" + +here=`pwd` +tmp=/tmp/$$ +status=1 # failure is the default! +trap "_cleanup; exit \$status" 0 1 2 3 15 + +_cleanup() +{ + cd / + rm -f $tmp.* +} + +# get standard environment, filters and checks +. ./common/rctests/ext4/048 line 36
Quoted 10 lines
tests/ext4/048 new file +10
-0+. ./common/filter + +# remove previous $seqres.full before test +rm -f $seqres.full + +# real QA test starts here + +# Modify as appropriate. +_supported_fs ext4 +_supported_fs genericext4 or generic? Tell the truth, according to below testing steps, I think it can be a generic test case, not only for ext4.
Quoted 5 lines
tests/ext4/048 new file +5
-0+_require_scratch +_require_xfs_io_command "falloc" + +dmesg -c > /dev/null +tests/ext4/048 line 51
Quoted 10 lines
tests/ext4/048 new file +10
-0+_scratch_mkfs > $seqres.full 2>&1 +_scratch_mount >> $seqres.full 2>&1 + +testdir=$SCRATCH_MNT +cd ${testdir} + +mkdir test +$XFS_IO_PROG -f -c "falloc 0 128M" img >> $seqres.full +$MKFS_EXT4_PROG img > /dev/null 2>&1 +$MOUNT_PROG img testCan we reproduce this bug by $SCRATCH_DEV directly, not through a loopdev. Likes:
Quoted 2 lines
_scratch_mkfs_sized128M (maybe bigger ?)_scratch_mount
I tried this:
dev_size=$((128 * 1024 * 1024))_scratch_mkfs_sized $dev_size >>$seqres.full 2>&1_scratch_mount
But it do not reproduce this bug. Maybe it should through a loopdev.
Quoted 17 lines
tests/ext4/048 line 54
Quoted 4 lines
tests/ext4/048 new file +3
-0+ +# fill the disk space +dd if=/dev/zero of=test/foo bs=1M count=128 > /dev/null 2>&1Can
_fill_fs()helper help you that?tests/ext4/048 line 62
Quoted 8 lines
tests/ext4/048 new file +8
-0+ +# create 1000 files, not all the files will be created successfully +mkdir test/dir +cd test/dir +for ((i = 0; i < 1000; i++)) +do + touch file$i > /dev/null 2>&1 +doneI don't know if it can be 100% sure there's at least 1 file will be created at here, after you tried to fill the fs.
Quoted 3 lines
So I think maybe you can create a file with known name, then use
_fill_fs()to fill the whole fs. Then try to rename the file you know its name. Can that reproduce the bug?
It can not repoduce the bug.
Quoted 28 lines
tests/ext4/048 line 73
Quoted 12 lines
tests/ext4/048 new file +11
-0+ +# try to rename, but now no space left on device +$here/src/renameat2 -w $testdir/test/dir/file1 $testdir/test/dir/dst_file + +cd $testdir +$UMOUNT_PROG test +$MOUNT_PROG img test +ls -l test/dir/file1 > /dev/null 2>&1 +$UMOUNT_PROG test + +dmesg -c | grep "deleted inode referenced"Can
_check_dmesg_for()help you?Quoted 14 lines
tests/ext4/048 new file +3
-0+# success, all done +status=0 +exittests/ext4/048.out new file +2
-0@@ -0,0 +1,2 @@ +QA output created by 048 +No space left on devicetests/ext4/group +0
-1--- a/tests/ext4/group
Quoted 8 lines
tests/ext4/group line 53
Quoted 6 lines
+++ b/tests/ext4/group
tests/ext4/group +1
-0@@ -50,6 +50,7 @@ 045 auto dir 046 auto prealloc quick 047 auto quick dax +048 otherI think your test case is a general test case, "auto"and "rename" groups are good to it, if it's quick enough, add "quick" group.
Maybe it is only ext4 test case, I think.
Thanks,
Sun Ke
Quoted 8 lines
Quoted 7 lines
tests/ext4/group +0
-0271 auto rw quick 301 aio auto ioctl rw stress defrag 302 aio auto ioctl rw stress defragSignature · 1 line
2.13.6.