From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: holger@applied-asynchrony.com, clm@fb.com, dsterba@suse.com,
xiaolong.ye@intel.com
Subject: [PATCH v2 2/2] btrfs: wait for bdev put
Date: Tue, 21 Jun 2016 18:24:08 +0800 [thread overview]
Message-ID: <1466504648-2937-1-git-send-email-anand.jain@oracle.com> (raw)
In-Reply-To: <1465901726-15490-2-git-send-email-anand.jain@oracle.com>
From: Anand Jain <Anand.Jain@oracle.com>
Further to the commit
bc178622d40d87e75abc131007342429c9b03351
btrfs: use rcu_barrier() to wait for bdev puts at unmount
This patch implements a method to time wait on the __free_device()
which actually does the bdev put. This is needed as the user space
running 'btrfs fi show -d' immediately after the replace and
unmount, is still reading older information from the device.
mail-archive.com/linux-btrfs@vger.kernel.org/msg54188.html
Signed-off-by: Anand Jain <anand.jain@oracle.com>
[updates: bc178622d40d87e75abc131007342429c9b03351]
---
v2: Also to make sure bdev_closing is set it needs rcu_barrier(),
restored rcu_barrier().
fs/btrfs/volumes.c | 45 +++++++++++++++++++++++++++++++++++++++++++--
fs/btrfs/volumes.h | 1 +
2 files changed, 44 insertions(+), 2 deletions(-)
diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
index 604daf315669..ef61c34cafbf 100644
--- a/fs/btrfs/volumes.c
+++ b/fs/btrfs/volumes.c
@@ -27,6 +27,7 @@
#include <linux/raid/pq.h>
#include <linux/semaphore.h>
#include <linux/uuid.h>
+#include <linux/delay.h>
#include <asm/div64.h>
#include "ctree.h"
#include "extent_map.h"
@@ -254,6 +255,17 @@ static struct btrfs_device *__alloc_device(void)
return dev;
}
+static int is_device_closing(struct list_head *head)
+{
+ struct btrfs_device *dev;
+
+ list_for_each_entry(dev, head, dev_list) {
+ if (dev->bdev_closing)
+ return 1;
+ }
+ return 0;
+}
+
static noinline struct btrfs_device *__find_device(struct list_head *head,
u64 devid, u8 *uuid)
{
@@ -832,12 +844,22 @@ again:
static void __free_device(struct work_struct *work)
{
struct btrfs_device *device;
+ struct btrfs_device *new_device_addr;
device = container_of(work, struct btrfs_device, rcu_work);
if (device->bdev)
blkdev_put(device->bdev, device->mode);
+ /*
+ * If we are coming here from btrfs_close_one_device()
+ * then it allocates a new device structure for the same
+ * devid, so find device again with the devid
+ */
+ new_device_addr = __find_device(&device->fs_devices->devices,
+ device->devid, NULL);
+
+ new_device_addr->bdev_closing = 0;
rcu_string_free(device->name);
kfree(device);
}
@@ -884,6 +906,12 @@ static void btrfs_close_one_device(struct btrfs_device *device)
list_replace_rcu(&device->dev_list, &new_device->dev_list);
new_device->fs_devices = device->fs_devices;
+ /*
+ * So to wait for kworkers to finish all blkdev_puts,
+ * so device is really free when umount is done.
+ */
+ new_device->bdev_closing = 1;
+
call_rcu(&device->rcu, free_device);
}
@@ -912,6 +940,7 @@ int btrfs_close_devices(struct btrfs_fs_devices *fs_devices)
{
struct btrfs_fs_devices *seed_devices = NULL;
int ret;
+ int retry_cnt = 5;
mutex_lock(&uuid_mutex);
ret = __btrfs_close_devices(fs_devices);
@@ -929,10 +958,22 @@ int btrfs_close_devices(struct btrfs_fs_devices *fs_devices)
}
/*
* Wait for rcu kworkers under __btrfs_close_devices
- * to finish all blkdev_puts so device is really
- * free when umount is done.
+ * to finish all free_device()
*/
rcu_barrier();
+
+ /*
+ * Wait for a grace period so that __free_device()
+ * will actaully do the device close.
+ */
+ while (is_device_closing(&fs_devices->devices) &&
+ --retry_cnt) {
+ mdelay(1000); //1 sec
+ }
+
+ if (!(retry_cnt > 0))
+ printk(KERN_WARNING "BTRFS: %pU bdev_put didn't complete, giving up\n",
+ fs_devices->fsid);
return ret;
}
diff --git a/fs/btrfs/volumes.h b/fs/btrfs/volumes.h
index 0ac90f8d85bd..945e49f5e17d 100644
--- a/fs/btrfs/volumes.h
+++ b/fs/btrfs/volumes.h
@@ -150,6 +150,7 @@ struct btrfs_device {
/* Counter to record the change of device stats */
atomic_t dev_stats_ccnt;
atomic_t dev_stat_values[BTRFS_DEV_STAT_VALUES_MAX];
+ int bdev_closing;
};
/*
--
2.7.0
next prev parent reply other threads:[~2016-06-21 10:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 9:27 [PULL] Btrfs for 4.7, part 2 David Sterba
2016-05-27 0:14 ` Chris Mason
2016-05-27 11:18 ` David Sterba
2016-05-27 14:35 ` Chris Mason
2016-05-27 15:42 ` Chris Mason
2016-05-28 5:14 ` Anand Jain
2016-05-29 12:21 ` Chris Mason
2016-06-14 10:52 ` Anand Jain
2016-06-14 10:55 ` [PATCH 1/2] btrfs: reorg btrfs_close_one_device() Anand Jain
2016-06-14 10:55 ` [PATCH 2/2] btrfs: wait for bdev put Anand Jain
2016-06-18 16:34 ` Holger Hoffstätte
2016-06-20 8:33 ` Anand Jain
2016-06-21 10:24 ` Anand Jain [this message]
2016-06-21 11:46 ` [PATCH v2 " Holger Hoffstätte
2016-06-21 13:00 ` Chris Mason
2016-06-22 10:18 ` Anand Jain
2016-06-22 21:47 ` Chris Mason
2016-06-23 13:07 ` Anand Jain
2016-06-23 12:54 ` [PATCH v3 2/2] btrfs: make sure device is synced before return Anand Jain
2016-06-23 14:27 ` Chris Mason
2016-07-08 14:13 ` 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=1466504648-2937-1-git-send-email-anand.jain@oracle.com \
--to=anand.jain@oracle.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=holger@applied-asynchrony.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=xiaolong.ye@intel.com \
/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).