From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: Anand Jain <anand.jain@oracle.com>
Subject: [PATCH 0/2 v2] btrfs: reject device with CHANGING_FSID_V2 flag
Date: Thu, 21 Sep 2023 05:51:12 +0800 [thread overview]
Message-ID: <cover.1695244296.git.anand.jain@oracle.com> (raw)
v2: Splits the patch into two parts: one for the new code to reject
devices with CHANGING_FSID_V2 and the second to remove the unused code.
The btrfs-progs code to reunite devices with the CHANGING_FSID_V2 flag,
which is ported from the kernel, can be found in the following btrfs-progs
patchset:
[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
Furthermore, when the kernel stops supporting the CHANGING_FSID_V2 flag,
we will need to update the btrfs-progs test case accordingly:
btrfs-progs: misc-tests/034-metadata-uuid remove kernel support
v1:
https://lore.kernel.org/linux-btrfs/02d59bdd7a8b778deb17e300354558498db59376.1692178060.git.anand.jain@oracle.com
Anand Jain (2):
btrfs: reject device with CHANGING_FSID_V2
btrfs: remove unused code related to the CHANGING_FSID_V2 flag
fs/btrfs/disk-io.c | 10 ---
fs/btrfs/volumes.c | 166 ++++-----------------------------------------
fs/btrfs/volumes.h | 1 -
3 files changed, 13 insertions(+), 164 deletions(-)
--
2.38.1
next reply other threads:[~2023-09-20 21:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 21:51 Anand Jain [this message]
2023-09-20 21:51 ` [PATCH 1/2] btrfs: reject device with CHANGING_FSID_V2 Anand Jain
2023-09-22 11:23 ` David Sterba
2023-09-22 12:40 ` Anand Jain
2023-09-20 21:51 ` [PATCH 2/2] btrfs: remove unused code related to the CHANGING_FSID_V2 flag Anand Jain
2023-09-25 16:58 ` [PATCH 0/2 v2] btrfs: reject device with " David Sterba
2023-09-25 23:56 ` Anand Jain
2023-09-27 17:43 ` David Sterba
2023-09-28 1:25 ` Anand Jain
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=cover.1695244296.git.anand.jain@oracle.com \
--to=anand.jain@oracle.com \
--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).