From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: Nikolay Borisov <nborisov@suse.com>, dsterba@suse.cz
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v4] btrfs: Remove received_uuid during received snapshot ro->rw switch
Date: Sun, 12 Nov 2017 18:11:22 +0100 [thread overview]
Message-ID: <56af8081-3ecb-7a70-0e9a-b05220c608b3@mendix.com> (raw)
In-Reply-To: <1507191773-23039-1-git-send-email-nborisov@suse.com>
On 10/05/2017 10:22 AM, Nikolay Borisov wrote:
> Currently when a read-only snapshot is received and subsequently its ro property
> is set to false i.e. switched to rw-mode the received_uuid of that subvol remains
> intact. However, once the received volume is switched to RW mode we cannot
> guaranteee that it contains the same data, so it makes sense to remove the
> received uuid. The presence of the received_uuid can also cause problems when
> the volume is being send.
>
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
> Suggested-by: David Sterba <dsterba@suse.cz>
> ---
>
> v4:
> * Put the uuid tree removal code after the lightweight 'send in progress'
> check and don't move btrfs_start_transaction as suggested by David
>
> v3:
> * Rework the patch considering latest feedback from David Sterba i.e.
> explicitly use btrfs_end_transaction
>
> fs/btrfs/ioctl.c | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
> index ee4ee7cbba72..9328c091854b 100644
> --- a/fs/btrfs/ioctl.c
> +++ b/fs/btrfs/ioctl.c
> @@ -1775,6 +1775,7 @@ static noinline int btrfs_ioctl_subvol_setflags(struct file *file,
> struct btrfs_trans_handle *trans;
> u64 root_flags;
> u64 flags;
> + bool clear_received_uuid = false;
> int ret = 0;
>
> if (!inode_owner_or_capable(inode))
> @@ -1824,6 +1825,7 @@ static noinline int btrfs_ioctl_subvol_setflags(struct file *file,
> btrfs_set_root_flags(&root->root_item,
> root_flags & ~BTRFS_ROOT_SUBVOL_RDONLY);
> spin_unlock(&root->root_item_lock);
> + clear_received_uuid = true;
> } else {
> spin_unlock(&root->root_item_lock);
> btrfs_warn(fs_info,
> @@ -1840,6 +1842,24 @@ static noinline int btrfs_ioctl_subvol_setflags(struct file *file,
> goto out_reset;
> }
>
> + if (clear_received_uuid) {
> + if (!btrfs_is_empty_uuid(root->root_item.received_uuid)) {
> + ret = btrfs_uuid_tree_rem(trans, fs_info,
> + root->root_item.received_uuid,
> + BTRFS_UUID_KEY_RECEIVED_SUBVOL,
> + root->root_key.objectid);
> +
> + if (ret && ret != -ENOENT) {
> + btrfs_abort_transaction(trans, ret);
> + btrfs_end_transaction(trans);
> + goto out_reset;
> + }
> +
> + memset(root->root_item.received_uuid, 0,
> + BTRFS_UUID_SIZE);
Shouldn't we also wipe the other related fields here, like stime, rtime,
stransid, rtransid?
> + }
> + }
> +
> ret = btrfs_update_root(trans, fs_info->tree_root,
> &root->root_key, &root->root_item);
> if (ret < 0) {
>
--
Hans van Kranenburg
next prev parent reply other threads:[~2017-11-12 17:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 14:27 [PATCH 1/2] btrfs: Abort transaction if btrfs_update_root fails in btrfs_ioctl_subvol_setflags Nikolay Borisov
2017-09-26 14:27 ` [RFC PATCH 2/2] btrfs: Remove received_uuid during received snapshot ro->rw switch Nikolay Borisov
2017-09-27 8:53 ` [PATCH v2] " Nikolay Borisov
2017-09-26 17:39 ` [PATCH 1/2] btrfs: Abort transaction if btrfs_update_root fails in btrfs_ioctl_subvol_setflags David Sterba
2017-09-27 8:48 ` Nikolay Borisov
2017-09-27 14:00 ` David Sterba
2017-09-27 14:28 ` Nikolay Borisov
2017-09-28 7:53 ` [PATCH 1/2] btrfs: Explicitly handle btrfs_update_root failure Nikolay Borisov
2017-09-28 7:53 ` [PATCH v3 2/2] btrfs: Remove received_uuid during received snapshot ro->rw switch Nikolay Borisov
2017-09-29 17:56 ` David Sterba
2017-09-29 19:15 ` Nikolay Borisov
2017-10-04 15:00 ` David Sterba
2017-10-05 8:22 ` [PATCH v4] " Nikolay Borisov
2017-10-05 9:03 ` Anand Jain
2017-10-06 17:24 ` David Sterba
2017-10-06 17:49 ` Hans van Kranenburg
2017-10-06 20:07 ` Andrei Borzenkov
2017-10-06 21:27 ` Hans van Kranenburg
2017-10-07 7:56 ` Andrei Borzenkov
2017-11-12 17:11 ` Hans van Kranenburg [this message]
2017-09-29 17:42 ` [PATCH 1/2] btrfs: Explicitly handle btrfs_update_root failure David Sterba
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=56af8081-3ecb-7a70-0e9a-b05220c608b3@mendix.com \
--to=hans.van.kranenburg@mendix.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.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;
as well as URLs for NNTP newsgroup(s).