From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH V2 3/3] Btrfs: device path change must be logged
Date: Mon, 5 Oct 2015 16:48:10 +0800 [thread overview]
Message-ID: <1444034890-9353-3-git-send-email-anand.jain@oracle.com> (raw)
In-Reply-To: <1444034890-9353-1-git-send-email-anand.jain@oracle.com>
>From the issue diagnosable point of view, log if the device path is
changed.
Signed-off-by: Anand Jain <anand.jain@oracle.com>
---
V2: Accepts David's review comment and adds a new ret value 2
for device_list_add() and based on that the caller function
would indicate if the path is overwritten (thanks David).
fs/btrfs/volumes.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
index e76cad3..b8b1171 100644
--- a/fs/btrfs/volumes.c
+++ b/fs/btrfs/volumes.c
@@ -504,6 +504,7 @@ void btrfs_free_stale_device(struct btrfs_device *cur_dev)
*
* Returns:
* 1 - first time device is seen
+ * 2 - device already known but now is overwritten with new path
* 0 - device already known
* < 0 - error
*/
@@ -603,6 +604,7 @@ static noinline int device_list_add(const char *path,
fs_devices->missing_devices--;
device->missing = 0;
}
+ ret = 2;
}
/*
@@ -1033,8 +1035,9 @@ int btrfs_scan_one_device(const char *path, fmode_t flags, void *holder,
ret = device_list_add(path, disk_super, devid, fs_devices_ret);
if (ret > 0) {
- printk(KERN_INFO "BTRFS: device fsid %pU devid %llu transid %llu %s\n",
- disk_super->fsid, devid, transid, path);
+ printk(KERN_INFO "BTRFS: device fsid %pU devid %llu transid %llu %s %s\n",
+ disk_super->fsid, devid, transid, path,
+ ret == 2 ? "(overwritten)":"");
ret = 0;
}
if (!ret && fs_devices_ret)
--
2.4.1
prev parent reply other threads:[~2015-10-05 8:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 8:48 [PATCH 1/3] Btrfs: create a helper function to read the disk super Anand Jain
2015-10-05 8:48 ` [PATCH V2 2/3] btrfs: maintain consistency in logging to help debugging Anand Jain
2015-10-05 8:48 ` Anand Jain [this message]
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=1444034890-9353-3-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).