From: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 1/4] Btrfs-progs: do not run ioctls in check_mounted_where()
Date: Wed, 18 Sep 2013 16:27:33 +0800 [thread overview]
Message-ID: <1379492856-30639-2-git-send-email-wangsl.fnst@cn.fujitsu.com> (raw)
In-Reply-To: <1379492856-30639-1-git-send-email-wangsl.fnst@cn.fujitsu.com>
We don't need to run ioctls when checking whether btrfs
has mounted somewhere.
Signed-off-by: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
---
utils.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/utils.c b/utils.c
index 134bf80..e3738d3 100644
--- a/utils.c
+++ b/utils.c
@@ -956,7 +956,7 @@ int check_mounted_where(int fd, const char *file, char *where, int size,
/* scan other devices */
if (is_btrfs && total_devs > 1) {
- if((ret = btrfs_scan_for_fsid(1)))
+ if((ret = btrfs_scan_for_fsid(0)))
return ret;
}
--
1.8.3.1
next prev parent reply other threads:[~2013-09-18 8:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 8:27 [PATCH 0/4] add super-recover tool to recover bad supers Wang Shilong
2013-09-18 8:27 ` Wang Shilong [this message]
2013-09-18 8:27 ` [PATCH 2/4] Btrfs-progs: pass flag to control whether run ioctl in btrfs_scan_for_fsid() Wang Shilong
2013-09-18 8:27 ` [PATCH 3/4] Btrfs-progs: move ask_user() to utils.c Wang Shilong
2013-09-18 8:27 ` [PATCH 4/4] Btrfs-progs: add super-recover to recover bad supers Wang Shilong
2013-09-18 15:13 ` David Sterba
2013-09-18 15:31 ` Wang Shilong
2013-09-18 16:31 ` David Sterba
2013-09-21 1:16 ` Wang Shilong
2013-09-23 12:10 ` [offlist] " David Sterba
2013-09-18 15:18 ` [PATCH 0/4] add super-recover tool " 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=1379492856-30639-2-git-send-email-wangsl.fnst@cn.fujitsu.com \
--to=wangsl.fnst@cn.fujitsu.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).