From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Zorro Lang <zlang@redhat.com>
Cc: jaegeuk@kernel.org, Zorro Lang <zlang@kernel.org>,
fstests@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 2/2] f2fs/022: fix to run testcase correctly
Date: Mon, 3 Nov 2025 09:53:39 +0800 [thread overview]
Message-ID: <207c9423-c776-4be1-a440-a3674d06416c@kernel.org> (raw)
In-Reply-To: <20251101114453.g6fxupmriauxtroc@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>
On 11/1/25 19:44, Zorro Lang wrote:
> On Mon, Oct 20, 2025 at 10:31:08AM +0800, Chao Yu wrote:
>> f2fs/022 will report failure as below:
>>
>> f2fs/022 - output mismatch (see /share/git/fstests/results//f2fs/022.out.bad)
>> --- tests/f2fs/022.out 2025-10-20 10:18:47.075968669 +0800
>> +++ /share/git/fstests/results//f2fs/022.out.bad 2025-10-20 10:25:20.000000000 +0800
>> @@ -1,2 +1,5 @@
>> QA output created by 022
>> +wrote 8388608/8388608 bytes at offset 0
>> +8 MiB, 2048 ops; 0.0018 sec (4.300 GiB/sec and 1127132.6362 ops/sec)
>> +fallocate: Operation not supported
>> Silence is golden
>> ...
>> (Run 'diff -u /share/git/fstests/tests/f2fs/022.out /share/git/fstests/results//f2fs/022.out.bad' to see the entire diff)
>>
>> HINT: You _MAY_ be missing kernel fix:
>> xxxxxxxxxxxx f2fs: fix to do sanity check on node footer for non inode dnode
>>
>> Fix this testcase as below:
>>
>> - fix a typo "$SCARTCH_MNT"
>> - fix to update output to "fallocate: Structure needs cleaning"
>> - relocate output of "$XFS_IO_PROG $foo_path -c "pwrite 0 8M"" to
>> $seqres.full
>>
>> Cc: Jaegeuk Kim <jaegeuk@kernel.org>
>> Signed-off-by: Chao Yu <chao@kernel.org>
>> ---
>> tests/f2fs/022 | 8 +++-----
>> tests/f2fs/022.out | 2 +-
>> 2 files changed, 4 insertions(+), 6 deletions(-)
>>
>> diff --git a/tests/f2fs/022 b/tests/f2fs/022
>> index f6d77c96..728ef4e8 100755
>> --- a/tests/f2fs/022
>> +++ b/tests/f2fs/022
>> @@ -24,15 +24,15 @@ _require_inject_f2fs_command node i_nid
>> # remove all mkfs options to avoid layout change of on-disk inode
>> export MKFS_OPTIONS=""
>>
>> -foo_path=$SCARTCH_MNT/foo
>> -bar_path=$SCARTCH_MNT/bar
>> +foo_path=$SCRATCH_MNT/foo
>> +bar_path=$SCRATCH_MNT/bar
>
> Hahaha, I took long time to find out what these 2 lines try to change:) Thanks
> for fixing this.
Haha, Seems I rebased v2 to a problematic codebase when I sync-up code from
different git repo. It took me some time to find the root cause of 022
failure. :/
Anyway, thanks for the review. :)
Thanks,
>
> Reviewed-by: Zorro Lang <zlang@redhat.com>
>
>>
>> _scratch_mkfs >> $seqres.full
>> _scratch_mount
>>
>> touch $foo_path
>> touch $bar_path
>> -$XFS_IO_PROG $foo_path -c "pwrite 0 8M"
>> +$XFS_IO_PROG $foo_path -c "pwrite 0 8M" >> $seqres.full
>> sync
>> foo_ino=`stat -c '%i' $foo_path`
>> bar_ino=`stat -c '%i' $bar_path`
>> @@ -48,7 +48,5 @@ _scratch_mount
>> $XFS_IO_PROG $foo_path -c "fpunch 6984k 4k"
>> _scratch_unmount
>>
>> -echo "Silence is golden"
>> -
>> status=0
>> exit
>> diff --git a/tests/f2fs/022.out b/tests/f2fs/022.out
>> index 394c6a7c..5307e3d7 100644
>> --- a/tests/f2fs/022.out
>> +++ b/tests/f2fs/022.out
>> @@ -1,2 +1,2 @@
>> QA output created by 022
>> -Silence is golden
>> +fallocate: Structure needs cleaning
>> --
>> 2.49.0
>>
>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2025-11-03 1:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 2:31 [f2fs-dev] [PATCH 1/2] f2fs: add commit id to _fixed_by_kernel_commit for f2fs/02[1-2] Chao Yu via Linux-f2fs-devel
2025-10-20 2:31 ` [f2fs-dev] [PATCH 2/2] f2fs/022: fix to run testcase correctly Chao Yu via Linux-f2fs-devel
2025-11-01 11:44 ` Zorro Lang via Linux-f2fs-devel
2025-11-03 1:53 ` Chao Yu via Linux-f2fs-devel [this message]
2025-11-01 11:40 ` [f2fs-dev] [PATCH 1/2] f2fs: add commit id to _fixed_by_kernel_commit for f2fs/02[1-2] Zorro Lang via Linux-f2fs-devel
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=207c9423-c776-4be1-a440-a3674d06416c@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=zlang@kernel.org \
--cc=zlang@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;
as well as URLs for NNTP newsgroup(s).