From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/4] btrfs: fix issues due to alien device
Date: Fri, 4 Oct 2019 15:49:59 +0800 [thread overview]
Message-ID: <1570175403-4073-1-git-send-email-anand.jain@oracle.com> (raw)
Alien device is a device in fs_devices list having a different fsid than
the expected fsid. This patch set fixes issues found due to the same.
Patch1: is a cleanup patch, not related.
Patch2: fixes the missing device not missing in the userland, by
hardening the function btrfs_open_one_device().
Patch3: fixes failing to mount a degraded RAID1 (but it can apply
to RAID5/6/10 as well), by hardening the function
btrfs_free_extra_devids().
Patch4: eliminates the source of the alien device in the fs_devices.
Anand Jain (4):
btrfs: drop useless goto in open_fs_devices
btrfs: delete identified alien device in open_fs_devices
btrfs: include non-missing as a qualifier for the latest_bdev
btrfs: free alien device due to device add
fs/btrfs/volumes.c | 40 ++++++++++++++++++++++++++++++----------
1 file changed, 30 insertions(+), 10 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-10-04 7:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 7:49 Anand Jain [this message]
2019-10-04 7:50 ` [PATCH 1/4] btrfs: drop useless goto in open_fs_devices Anand Jain
2019-10-04 8:12 ` Nikolay Borisov
2019-10-04 7:50 ` [PATCH 2/4] btrfs: delete identified alien device " Anand Jain
2019-10-04 8:18 ` Nikolay Borisov
2019-10-06 2:47 ` [PATCH v2 " Anand Jain
2019-10-06 11:44 ` Nikolay Borisov
2019-10-06 2:51 ` [PATCH " Anand Jain
2019-10-04 7:50 ` [PATCH 3/4] btrfs: include non-missing as a qualifier for the latest_bdev Anand Jain
2019-10-04 8:11 ` Nikolay Borisov
2019-10-04 9:08 ` [Not TLS] " Graham Cobb
2019-10-04 9:20 ` Nikolay Borisov
2019-10-04 7:50 ` [PATCH 4/4] btrfs: free alien device due to device add Anand Jain
2019-10-04 8:19 ` [PATCH 0/4] btrfs: fix issues due to alien device Nikolay Borisov
2019-10-07 9:42 ` 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=1570175403-4073-1-git-send-email-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).