From: "gux.fnst" <gux.fnst@cn.fujitsu.com>
To: "Lukáš Czerner" <lczerner@redhat.com>,
"Dave Chinner" <david@fromorbit.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] xfstests: add test for ext4 fallocate collapse range check
Date: Wed, 25 Jun 2014 18:05:09 +0800 [thread overview]
Message-ID: <53AA9ED5.5080408@cn.fujitsu.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1406191105220.2182@localhost.localdomain>
On 06/19/2014 05:12 PM, Lukáš Czerner wrote:
> On Thu, 19 Jun 2014, Xing Gu wrote:
>
>> Date: Thu, 19 Jun 2014 13:50:04 +0800
>> From: Xing Gu <gux.fnst@cn.fujitsu.com>
>> To: fstests@vger.kernel.org
>> Cc: Xing Gu <gux.fnst@cn.fujitsu.com>
>> Subject: [PATCH] xfstests: add test for ext4 fallocate collapse range check
>>
>> +
>> +testfile=$SCRATCH_MNT/file.$seq
>> +# fcollapse/truncate continuously and simultaneously
>> +# a same file
>> +for ((i=1; i <= 100; i++))
>> +do
>> + while true;do
>> + $XFS_IO_PROG -f -c 'truncate 100k' $testfile 2>> $seqres.full
>> + $XFS_IO_PROG -f -c 'fcollapse 0 16k' $testfile 2>> $seqres.full
>> + done &
>> + PIDS="$PIDS $!"
>> + while true;do
>> + $XFS_IO_PROG -f -c 'truncate 0' $testfile 2>> $seqres.full
>> + done &
>> + PIDS="$PIDS $!"
>
> It does not look like it's just checking whether we correctly bail
> out if collapse range ends past i_size, but rather it's checking for
> the truncate/collapse range race.
>
> Also in description you're saying that we need to make sure that
> i_size is not going to change, which is not tested here at all.
>
> So I think that you need to split it in two tests:
>
> - test truncate/collapse range race (what is the failure
> condition?)
> - test whether we correctly bail out when collapse range is past
> i_size and make sure that i_size did not change at all.
Indeed, this case is not ext4 specific, and just checks for the
truncate/collapse range race.
If this case is needed by xfstests, I will modify the classification and
description of this case according to your comment.
Thanks for your review!
Regards,
Xing Gu
>
> Thanks!
> -Lukas
>
>> +done
>> +# sleep for 180s, BUG_ON is triggered within 3 minutes
>> +# in most case
>> +sleep 180
>> +
>> +new_bug=`dmesg | grep -c "kernel BUG"`
>> +if [ $new_bug -ne $old_bug ]; then
>> + echo "kernel bug detected, check dmesg for more infomation."
>> +fi
>> +
>> +kill $PIDS >/dev/null 2>&1
>> +wait
>> +status=0
>> +exit
>> diff --git a/tests/ext4/307.out b/tests/ext4/307.out
>> new file mode 100644
>> index 0000000..260c17c
>> --- /dev/null
>> +++ b/tests/ext4/307.out
>> @@ -0,0 +1 @@
>> +QA output created by 307
>> diff --git a/tests/ext4/group b/tests/ext4/group
>> index 7e66035..0f1852f 100644
>> --- a/tests/ext4/group
>> +++ b/tests/ext4/group
>> @@ -12,3 +12,4 @@
>> 304 aio dangerous ioctl rw stress
>> 305 auto
>> 306 auto rw resize quick
>> +307 auto
>>
> .
>
next prev parent reply other threads:[~2014-06-25 10:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 5:50 [PATCH] xfstests: add test for ext4 fallocate collapse range check Xing Gu
2014-06-19 6:56 ` Dave Chinner
2014-06-25 10:05 ` gux.fnst
2014-06-19 9:12 ` Lukáš Czerner
2014-06-25 10:05 ` gux.fnst [this message]
2014-09-17 10:03 ` [PATCH v2] xfstests: add test for truncate/collapse range race Xing Gu
2014-09-25 3:55 ` Eryu Guan
2014-09-30 9:50 ` [PATCH v3] " Xing Gu
2014-10-22 9:56 ` gux.fnst
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53AA9ED5.5080408@cn.fujitsu.com \
--to=gux.fnst@cn.fujitsu.com \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=lczerner@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox