From: Anand Jain <anand.jain@oracle.com>
To: dsterba@suse.cz
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: misc-tests/034-metadata-uuid remove kernel support
Date: Tue, 3 Oct 2023 15:49:06 +0800 [thread overview]
Message-ID: <d433f793-3277-f07f-3bdf-2a60301aa234@oracle.com> (raw)
In-Reply-To: <20231002171050.GW13697@twin.jikos.cz>
-reload_btrfs() {
- run_check $SUDO_HELPER rmmod btrfs
- run_check $SUDO_HELPER modprobe btrfs
On 3/10/23 01:10, David Sterba wrote:
> On Thu, Sep 21, 2023 at 06:35:10AM +0800, Anand Jain wrote:
>> The kernel patch, ("btrfs: reject device with CHANGING_FSID_V2 flag"),
>> removes kernel support for the CHANGING_FSID_V2 flag. So, drop its
>> related testcase.
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>> ---
>> Apply this on top of
>>
>> [PATCH 0/4 v4] btrfs-progs: recover from failed metadata_uuid port kernel
>> btrfs-progs: tune use the latest bdev in fs_devices for super_copy
>> btrfs-progs: add support to fix superblock with CHANGING_FSID_V2 flag
>> btrfs-progs: recover from the failed btrfstune -m|M
>> btrfs-progs: test btrfstune -m|M ability to fix previous failures
>
> The above patches are now in devel but the test still fails because you
> haven't removed the check for builtin/module status of btrfs.
It was removed. From your devel branch.
$ git log -p 86b1e47c80d62519975eae95b39ea053a220abec
commit 86b1e47c80d62519975eae95b39ea053a220abec
Author: Anand Jain <anand.jain@oracle.com>
Date: Thu Sep 21 06:35:10 2023 +0800
btrfs-progs: test: misc/034 remove kernel support
::
-reload_btrfs() {
- run_check $SUDO_HELPER rmmod btrfs
- run_check $SUDO_HELPER modprobe btrfs
}
prev parent reply other threads:[~2023-10-03 7:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 22:35 [PATCH] btrfs-progs: misc-tests/034-metadata-uuid remove kernel support Anand Jain
2023-10-02 17:10 ` David Sterba
2023-10-03 7:49 ` 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=d433f793-3277-f07f-3bdf-2a60301aa234@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
/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).