summaryrefslogtreecommitdiffstats
path: root/fs/btrfs/super.c
diff options
context:
space:
mode:
authorAnand Jain <Anand.Jain@oracle.com>2017-12-18 10:08:59 +0100
committerDavid Sterba <dsterba@suse.com>2018-01-22 16:08:20 +0100
commit6528b99d3d20795ff947d9b3fd736affe901acef (patch)
treee184957907d6a57cd0c1b53e193e07b9e39ea352 /fs/btrfs/super.c
parentbtrfs: sink unlock_extent parameter gfp_flags (diff)
downloadlinux-6528b99d3d20795ff947d9b3fd736affe901acef.tar.xz
linux-6528b99d3d20795ff947d9b3fd736affe901acef.zip
btrfs: factor btrfs_check_rw_degradable() to check given device
Update btrfs_check_rw_degradable() to check against the given device if its lost. We can use this function to know if the volume is going to be in degraded mode OR failed state, when the given device fails. Which is needed when we are handling the device failed state. A preparatory patch does not affect the flow as such. Signed-off-by: Anand Jain <anand.jain@oracle.com> Reviewed-by: Qu Wenruo <wqu@suse.com> [ enhance comment ] Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/super.c')
-rw-r--r--fs/btrfs/super.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
index f40352843c0b..8af7590a5638 100644
--- a/fs/btrfs/super.c
+++ b/fs/btrfs/super.c
@@ -1844,7 +1844,7 @@ static int btrfs_remount(struct super_block *sb, int *flags, char *data)
goto restore;
}
- if (!btrfs_check_rw_degradable(fs_info)) {
+ if (!btrfs_check_rw_degradable(fs_info, NULL)) {
btrfs_warn(fs_info,
"too many missing devices, writeable remount is not allowed");
ret = -EACCES;