From: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
To: Eryu Guan <guaneryu@gmail.com>
Cc: <fstests@vger.kernel.org>
Subject: Re: [PATCH] ext4/046: skip test when ext4 doesn't support bs < ps with dioread_nolock
Date: Tue, 19 Jan 2021 11:00:27 +0800 [thread overview]
Message-ID: <60064B4B.1060108@cn.fujitsu.com> (raw)
In-Reply-To: <20210117150624.GA2347@desktop>
Hi Eryu
> On Thu, Jan 14, 2021 at 11:55:03AM +0800, Yang Xu wrote:
>> When testing arm machine, this case fails because ps> bs and kernel doesn't
>> introduced commit c8cc88163f40 ("ext4: Add support for blocksize< pagesize in dioread_nolock").
>> Only skip this case when mounting failed.
>
> Perhaps it's the kernel that should be fixed? i.e. backport the
> mentioned patch? Depends on if we treat it as a bug or a feature I
> think..
IMO, it is a feature instead of a bug.
>
>>
>> Signed-off-by: Yang Xu<xuyang2018.jy@cn.fujitsu.com>
>> ---
>> tests/ext4/046 | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/tests/ext4/046 b/tests/ext4/046
>> index 5524024e..e307cbf1 100755
>> --- a/tests/ext4/046
>> +++ b/tests/ext4/046
>> @@ -37,7 +37,8 @@ _require_xfs_io_command "falloc"
>> _require_scratch_size $((6 * 1024 * 1024)) #kB
>>
>> _scratch_mkfs>> $seqres.full 2>&1
>> -_scratch_mount "-o dioread_nolock">> $seqres.full 2>&1
>> +_try_scratch_mount "-o dioread_nolock">>$seqres.full 2>&1 || \
>> + _notrun "mount failed, ext4 doesn't support bs< ps with dioread_nolock?"
>
> At least we should check if it's really the bs< ps case before _notrun
> the test, otherwise we may fail to find dioread_nolock mount regression.
Ok. Will send v2.
>
> Thanks,
> Eryu
>
>>
>> # Get blksz
>> blksz=$(_get_file_block_size $SCRATCH_MNT)
>> --
>> 2.23.0
>>
>>
>
>
> .
>
next prev parent reply other threads:[~2021-01-19 3:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 3:55 [PATCH] ext4/046: skip test when ext4 doesn't support bs < ps with dioread_nolock Yang Xu
2021-01-17 15:06 ` Eryu Guan
2021-01-19 3:00 ` Yang Xu [this message]
2021-01-19 3:48 ` Theodore Ts'o
2021-01-19 6:13 ` [PATCH v2] " Yang Xu
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=60064B4B.1060108@cn.fujitsu.com \
--to=xuyang2018.jy@cn.fujitsu.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.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