From: Zorro Lang <zlang@redhat.com>
To: Yongcheng Yang <yoyang@redhat.com>
Cc: fstests@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH fstests v3 2/2] generic/578: add a check to ensure that fiemap is supported
Date: Wed, 30 Aug 2023 20:55:44 +0800 [thread overview]
Message-ID: <20230830125544.chmzf5trejj4tppz@zlang-mailbox> (raw)
In-Reply-To: <ZO6vh5+ZLdLSFbB7@yoyang-vm.hosts.qa.psi.pek2.redhat.com>
On Wed, Aug 30, 2023 at 10:55:03AM +0800, Yongcheng Yang wrote:
> Hi Zorro,
>
> Can we assume all the FIEMAP tests need this check first?
> If so, there are some others need the same patch.
>
> I.e.
> [yoyang@yoyang-vm xfstests-dev]$ grep url .git/config
> url = git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
> [yoyang@yoyang-vm xfstests-dev]$ git pl
> Already up to date.
> [yoyang@yoyang-vm xfstests-dev]$ git grep _begin_fstest tests/ | grep fiemap | wc -l
> 101
> [yoyang@yoyang-vm xfstests-dev]$ git grep _require_xfs_io_command tests/ | grep fiemap | wc -l
> 86
> [yoyang@yoyang-vm xfstests-dev]$
Hi Yongcheng,
Thanks for taking attention on it. 101 - 86 = 15, let's check these 15 cases
one by one:
[zorro@zlang-laptop xfstests-dev]$ for i in `egrep -rsnl _begin_fstest.*fiemap tests`;do grep -q $i < <(egrep -rsnl _require_xfs_io_command.*fiemap tests) || echo $i;done
tests/btrfs/079
tests/btrfs/140
tests/btrfs/004
tests/ext4/001
tests/ext4/308
tests/generic/655
tests/generic/654
tests/generic/578
tests/generic/541
tests/generic/542
tests/generic/516
tests/generic/519
tests/generic/540
tests/generic/543
tests/overlay/066
btrfs/079: It doesn't use fiemap direclty, it use filefrag command to trigger
fiemap (if support). If FIEMAP is not supported then filefrag will
fall back to using FIBMAP. So it's not necessary to _notrun this case
if FIEMAP isn't supported I think.
btrfs/140: Similar as above
btrfs/004: Similar as above
ext4/001: It use fiemap through _test_generic_punch helper, so I think it should
has "_require_xfs_io_command fiemap"
ext4/308: I think it missed the `_require_xfs_io_command fiemap`
g/655: It doesn't use fiemap, but use filefrag. And filefrag will fall back to
FIBMAP, if FIEMAP isn't supported.
g/654: Similar as above
g/578: Similar as above
g/541: Similar as above
g/542: Similar as above
g/516: Similar as above
g/519: Similar as above
g/540: Similar as above
g/543: Similar as above
overlay/066: Similar as above
(If anything I said above is wrong, feel free to tell me:)
So I think ext4/001 and ext4/308 can have the `_require_xfs_io_command fiemap`.
But as they're ext4 specific test cases (not generic), so they won't affect
other fs (which doesn't support fiemap) testing. If you'd like, you can add
`_require_xfs_io_command fiemap` to these two cases.
Thanks,
Zorro
>
> Best Regards,
> Yongcheng
>
prev parent reply other threads:[~2023-08-30 18:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 17:56 [PATCH fstests v3 0/2] fstests: add appropriate checks for fs features for some tests Jeff Layton
2023-08-25 17:56 ` [PATCH fstests v3 1/2] common/attr: fix the _require_acl test Jeff Layton
2023-08-25 17:56 ` [PATCH fstests v3 2/2] generic/578: add a check to ensure that fiemap is supported Jeff Layton
2023-08-30 2:55 ` Yongcheng Yang
2023-08-30 12:55 ` Zorro Lang [this message]
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=20230830125544.chmzf5trejj4tppz@zlang-mailbox \
--to=zlang@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=yoyang@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