linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 1/2] btrfs: make code easy to read in btrfs_open_one_device()
Date: Mon, 22 Jan 2018 13:51:22 +0800	[thread overview]
Message-ID: <20180122055123.10404-1-anand.jain@oracle.com> (raw)

From: Anand Jain <Anand.Jain@oracle.com>

First set the usual case that is writeable, then check
for any special case like a seed device or a rdonly device
and set the state appropriately.

Signed-off-by: Anand Jain <anand.jain@oracle.com>
---
v1->v2:
 Add comment and commit log to explain its safe to set writeable
 first and then reset to the special case such as seed or readonly
 device. (no code change).

 fs/btrfs/volumes.c | 14 +++++++++-----
 1 file changed, 9 insertions(+), 5 deletions(-)

diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
index 5750cd9df417..001894782d84 100644
--- a/fs/btrfs/volumes.c
+++ b/fs/btrfs/volumes.c
@@ -689,14 +689,18 @@ static int btrfs_open_one_device(struct btrfs_fs_devices *fs_devices,
 
 	device->generation = btrfs_super_generation(disk_super);
 
+	/*
+	 * Set the device as writeable and then check if its
+	 * seed or readonly device. Both SUPER_FLAG_SEEDING and
+	 * bdev_read_only(bdev) can be set by the user when device
+	 * is unmounted. And this fn is called at the time of mount.
+	 */
+	set_bit(BTRFS_DEV_STATE_WRITEABLE, &device->dev_state);
 	if (btrfs_super_flags(disk_super) & BTRFS_SUPER_FLAG_SEEDING) {
 		clear_bit(BTRFS_DEV_STATE_WRITEABLE, &device->dev_state);
 		fs_devices->seeding = 1;
-	} else {
-		if (bdev_read_only(bdev))
-			clear_bit(BTRFS_DEV_STATE_WRITEABLE, &device->dev_state);
-		else
-			set_bit(BTRFS_DEV_STATE_WRITEABLE, &device->dev_state);
+	} else if (bdev_read_only(bdev)) {
+		clear_bit(BTRFS_DEV_STATE_WRITEABLE, &device->dev_state);
 	}
 
 	q = bdev_get_queue(bdev);
-- 
2.15.0


             reply	other threads:[~2018-01-22  5:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-22  5:51 Anand Jain [this message]
2018-01-22  5:51 ` [PATCH v2 2/2] btrfs: optimize move uuid_mutex closer to the critical section Anand Jain
  -- strict thread matches above, loose matches on Subject: below --
2018-01-22  6:31 [PATCH v2 1/2] btrfs: make code easy to read in btrfs_open_one_device() 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=20180122055123.10404-1-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).