From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>, <dsterba@suse.cz>
Subject: Re: [PATCH] btrfs-progs: Fix a bug which makes unfinished fsid change unrecoverable.
Date: Thu, 21 May 2015 10:24:21 +0800 [thread overview]
Message-ID: <555D41D5.10109@cn.fujitsu.com> (raw)
In-Reply-To: <1431671795-30516-1-git-send-email-quwenruo@cn.fujitsu.com>
Hi David,
I didn't see this patch merged into 4.0.1.
As without this patch, canceled fsid change process can't be recovered.
I totally understand that it's not good to merge a patch into the
already fully tested tree.
So would you please consider add this patch to next release(even 4.1 is OK)?
Thanks,
Qu
-------- Original Message --------
Subject: [PATCH] btrfs-progs: Fix a bug which makes unfinished fsid
change unrecoverable.
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>
Date: 2015年05月15日 14:36
> This bug is found by making break point after change_fsid_prepare() and
> then kill the unfinished change, then try to restore the unfinished fsid
> change.
>
> If fsid change is canceled, open_ctree will still fail even with
> IGNORE_FSID_MIMATCH open ctree flag, since it can't find device with
> mismatched fsid, making it unable to restoring.
>
> Now add ignore_fsid_mismatch judgment in btrfs_find_device() to fix the
> bug and allow later restore to work as expected.
>
> Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
> ---
> volumes.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/volumes.c b/volumes.c
> index 14ce33e..f7462c5 100644
> --- a/volumes.c
> +++ b/volumes.c
> @@ -1510,7 +1510,8 @@ struct btrfs_device *btrfs_find_device(struct btrfs_root *root, u64 devid,
> cur_devices = root->fs_info->fs_devices;
> while (cur_devices) {
> if (!fsid ||
> - !memcmp(cur_devices->fsid, fsid, BTRFS_UUID_SIZE)) {
> + (!memcmp(cur_devices->fsid, fsid, BTRFS_UUID_SIZE) ||
> + root->fs_info->ignore_fsid_mismatch)) {
> device = __find_device(&cur_devices->devices,
> devid, uuid);
> if (device)
>
next prev parent reply other threads:[~2015-05-21 2:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 6:36 [PATCH] btrfs-progs: Fix a bug which makes unfinished fsid change unrecoverable Qu Wenruo
2015-05-21 2:24 ` Qu Wenruo [this message]
2015-05-21 8:52 ` David Sterba
2015-05-26 15:26 ` 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=555D41D5.10109@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.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).