From: Anand Jain <anand.jain@oracle.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>,
Eric Sandeen <sandeen@sandeen.net>,
linux-btrfs@vger.kernel.org
Cc: fstests@vger.kernel.org
Subject: Re: xfstests seems broken on btrfs with multi-dev TEST_DEV
Date: Fri, 26 Feb 2021 11:10:05 +0800 [thread overview]
Message-ID: <680adeb5-7ae5-12af-36be-25f72fe9efb5@oracle.com> (raw)
In-Reply-To: <d7183517-95e5-7b75-3909-1b2d30db3a87@gmx.com>
On 25/02/2021 11:18, Qu Wenruo wrote:
>
>
> On 2021/2/25 上午11:15, Eric Sandeen wrote:
>> On 2/24/21 9:13 PM, Qu Wenruo wrote:
>>
>>> Now this makes way more sense,
>>
>> Sorry for the earlier mistake.
>>
>>> as your previous comment on
>>> _btrfs_forget_or_module_reload is completely correct.
>>>
>>> _btrfs_forget_or_module_reload will really forget all devices, while
>>> what we really want is just excluding certain devices, and not to affect
>>> the other ones.
>>>
>>> The proper way to fix it is to only introduce _btrfs_forget to
>>> unregister involved devices, not all.
>>>
>>> I'll take a look into the fix, but I'm afraid that, for systems which
>>> don't support forget, they have to skip those tests and reduce the
>>> coverage for older kernel/progs.
>>
>> Can't you just rescan when the test is done?
>
> Oh, that's way more simpler.
>
> Thanks for the tip, I just over-engineered.....
>
Yep agreed.
on kernels with forget-ioctl,
btrfs dev scan --forget $SCRATCH_DEV_POOL
shall suffice.
However if we could define TEST_DEV_POOL="dev1 dev2 dev3" it will help
both old/new kernels. IMO.
_btrfs_forget_or_module_reload()
{
::
btrfs dev scan $TEST_DEV_POOL
}
Thanks, Anand
> Thanks,
> Qu
>>
>>> Thanks,
>>> Qu
>>>
prev parent reply other threads:[~2021-02-26 3:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 16:12 xfstests seems broken on btrfs with multi-dev TEST_DEV Eric Sandeen
2021-02-24 21:39 ` Eric Sandeen
2021-02-25 1:16 ` Anand Jain
2021-02-25 1:46 ` Eric Sandeen
2021-02-25 1:56 ` Qu Wenruo
2021-02-25 2:45 ` Eric Sandeen
2021-02-25 3:13 ` Qu Wenruo
2021-02-25 3:15 ` Eric Sandeen
2021-02-25 3:18 ` Qu Wenruo
2021-02-26 3:10 ` Anand Jain [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=680adeb5-7ae5-12af-36be-25f72fe9efb5@oracle.com \
--to=anand.jain@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=sandeen@sandeen.net \
/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).