linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH 1/2] btrfs: remove check for BTRFS_FS_STATE_ERROR which we just set
@ 2018-01-04 10:01 Anand Jain
  2018-01-04 10:01 ` [PATCH 2/2] btrfS: collapse btrfs_handle_error() into __btrfs_handle_fs_error() Anand Jain
  2018-01-04 13:21 ` [PATCH 1/2] btrfs: remove check for BTRFS_FS_STATE_ERROR which we just set Nikolay Borisov
  0 siblings, 2 replies; 5+ messages in thread
From: Anand Jain @ 2018-01-04 10:01 UTC (permalink / raw)
  To: linux-btrfs

__btrfs_handle_fs_error() sets BTRFS_FS_STATE_ERROR, and calls
btrfs_handle_error() so no need to check if the BTRFS_FS_STATE_ERROR
is set in btrfs_handle_error(). And there is no other user of
btrfs_handle_error() as well.

Signed-off-by: Anand Jain <anand.jain@oracle.com>
---
 fs/btrfs/super.c | 26 ++++++++++++--------------
 1 file changed, 12 insertions(+), 14 deletions(-)

diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
index 4c49bb5632a2..60766f8ca434 100644
--- a/fs/btrfs/super.c
+++ b/fs/btrfs/super.c
@@ -113,20 +113,18 @@ static void btrfs_handle_error(struct btrfs_fs_info *fs_info)
 	if (sb_rdonly(sb))
 		return;
 
-	if (test_bit(BTRFS_FS_STATE_ERROR, &fs_info->fs_state)) {
-		sb->s_flags |= SB_RDONLY;
-		btrfs_info(fs_info, "forced readonly");
-		/*
-		 * Note that a running device replace operation is not
-		 * canceled here although there is no way to update
-		 * the progress. It would add the risk of a deadlock,
-		 * therefore the canceling is omitted. The only penalty
-		 * is that some I/O remains active until the procedure
-		 * completes. The next time when the filesystem is
-		 * mounted writeable again, the device replace
-		 * operation continues.
-		 */
-	}
+	sb->s_flags |= SB_RDONLY;
+	btrfs_info(fs_info, "forced readonly");
+	/*
+	 * Note that a running device replace operation is not
+	 * canceled here although there is no way to update
+	 * the progress. It would add the risk of a deadlock,
+	 * therefore the canceling is omitted. The only penalty
+	 * is that some I/O remains active until the procedure
+	 * completes. The next time when the filesystem is
+	 * mounted writeable again, the device replace
+	 * operation continues.
+	 */
 }
 
 /*
-- 
2.15.0


^ permalink raw reply related	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2018-01-05 13:02 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-01-04 10:01 [PATCH 1/2] btrfs: remove check for BTRFS_FS_STATE_ERROR which we just set Anand Jain
2018-01-04 10:01 ` [PATCH 2/2] btrfS: collapse btrfs_handle_error() into __btrfs_handle_fs_error() Anand Jain
2018-01-04 12:11   ` Nikolay Borisov
2018-01-05 13:00     ` David Sterba
2018-01-04 13:21 ` [PATCH 1/2] btrfs: remove check for BTRFS_FS_STATE_ERROR which we just set Nikolay Borisov

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).