From: Anand Jain <anand.jain@oracle.com>
To: fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, fdmanana@kernel.org
Subject: [PATCH 0/6 v3] btrfs/219 cloned-device mount capability update
Date: Mon, 30 Oct 2023 22:15:02 +0800 [thread overview]
Message-ID: <cover.1698674332.git.anand.jain@oracle.com> (raw)
v3:
Split changes into smaller discrete patches.
Add a helper function to check if the temp-fsid is supported.
Check for the second failure only when the temp-fsid is not supported.
v2:
Patch 1/2 has been added, which performs the cleanup of the local
variables and the _clean_up() function. Patch 2/2 in v2 restores
the code where it tests clone-device that it does not mount if the
temp-fsid feature is not present in the kernel.
Fixes btrfs/219 bug when temp-fsid is supported in the kernel.
Anand Jain (6):
common/rc: _fs_sysfs_dname fetch fsid using btrfs tool
common/rc: _destroy_loop_device confirm arg1 is set
common/btrfs: add helper _has_btrfs_sysfs_feature_attr
btrfs/219: fix _cleanup() to successful release the loop-device
btrfs/219: cloned-device mount capability update
btrfs/219: add to the auto group
common/btrfs | 12 ++++++++
common/rc | 10 +++++--
tests/btrfs/219 | 74 ++++++++++++++++++++++++++++---------------------
3 files changed, 63 insertions(+), 33 deletions(-)
--
2.39.3
next reply other threads:[~2023-10-30 14:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 14:15 Anand Jain [this message]
2023-10-30 14:15 ` [PATCH 1/6 v3] common/rc: _fs_sysfs_dname fetch fsid using btrfs tool Anand Jain
2023-10-30 16:16 ` Filipe Manana
2023-10-30 23:48 ` Anand Jain
2023-10-30 14:15 ` [PATCH 2/6 v3] common/rc: _destroy_loop_device confirm arg1 is set Anand Jain
2023-10-30 16:21 ` Filipe Manana
2023-10-30 23:48 ` Anand Jain
2023-10-30 14:15 ` [PATCH 3/6 v3] common/btrfs: add helper _has_btrfs_sysfs_feature_attr Anand Jain
2023-10-30 16:23 ` Filipe Manana
2023-10-30 23:29 ` Anand Jain
2023-10-31 11:34 ` Filipe Manana
2023-10-30 14:15 ` [PATCH 4/6 v3] btrfs/219: fix _cleanup() to successful release the loop-device Anand Jain
2023-10-30 16:29 ` Filipe Manana
2023-11-02 11:28 ` [PATCH v4 0/5] btrfs/219 cloned-device mount capability update Anand Jain
2023-10-31 0:53 ` [PATCH v4 3/5] btrfs/219: fix _cleanup() to successful release the loop-device Anand Jain
2023-10-31 11:41 ` Filipe Manana
2023-10-31 14:32 ` Anand Jain
2023-11-01 11:20 ` Zorro Lang
2023-11-02 11:37 ` Anand Jain
2023-11-02 11:28 ` Anand Jain
2023-11-02 11:28 ` [PATCH v4 1/5] common/rc: _fs_sysfs_dname fetch fsid using btrfs tool Anand Jain
2023-11-02 20:00 ` David Sterba
2023-11-02 23:01 ` Anand Jain
2023-11-02 11:28 ` [PATCH v4 2/5] common/btrfs: add helper _has_btrfs_sysfs_feature_attr Anand Jain
2023-11-02 11:28 ` [PATCH v4 4/5] btrfs/219: cloned-device mount capability update Anand Jain
2023-11-02 11:28 ` [PATCH v4 5/5] btrfs/219: add to the auto group Anand Jain
2023-10-30 14:15 ` [PATCH 5/6 v3] btrfs/219: cloned-device mount capability update Anand Jain
2023-10-30 16:31 ` Filipe Manana
2023-10-30 14:15 ` [PATCH 6/6 v3] btrfs/219: add to the auto group Anand Jain
2023-10-30 16:32 ` Filipe Manana
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.1698674332.git.anand.jain@oracle.com \
--to=anand.jain@oracle.com \
--cc=fdmanana@kernel.org \
--cc=fstests@vger.kernel.org \
--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