From: Eric Sandeen <sandeen@redhat.com>
To: linux-btrfs <linux-btrfs@vger.kernel.org>,
Jan Safranek <jsafrane@redhat.com>
Subject: [PATCH V2] btrfs: close any open devices if btrfs_mount fails
Date: Thu, 04 Apr 2013 11:32:31 -0500 [thread overview]
Message-ID: <515DAB1F.2050308@redhat.com> (raw)
In-Reply-To: <515D9DDE.5040306@redhat.com>
This:
# mkfs.btrfs /dev/sdb{1,2} ; wipefs -a /dev/sdb1; mount /dev/sdb2 /mnt/test
would lead to a blkdev open/close mismatch when the mount fails, and
a permanently busy (opened O_EXCL) sdb2:
# wipefs -a /dev/sdb2
wipefs: error: /dev/sdb2: probing initialization failed: Device or resource busy
It's because btrfs_open_devices() may open some devices, and still
return failure. So the error unwinding needs to close any open
devices in fs_devices before returning.
Reported-by: Jan Safranek <jsafrane@redhat.com>
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
V2: use open_devices not opened, that seems like the right test...
if a test is necessary I'm not certain, tbh. Seems prudently
defensive.
Note, __btrfs_open_devices is weird; it seems to return success or
failure based on the outcome of the result of the last call
to btrfs_get_bdev_and_sb(). But that's a different bug...
diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
index f6b8859..60c67fa 100644
--- a/fs/btrfs/super.c
+++ b/fs/btrfs/super.c
@@ -1125,7 +1125,7 @@ static struct dentry *btrfs_mount(struct file_system_type *fs_type, int flags,
error = btrfs_open_devices(fs_devices, mode, fs_type);
if (error)
- goto error_fs_info;
+ goto error_close_devices;
if (!(flags & MS_RDONLY) && fs_devices->rw_devices == 0) {
error = -EACCES;
@@ -1161,7 +1161,8 @@ static struct dentry *btrfs_mount(struct file_system_type *fs_type, int flags,
return root;
error_close_devices:
- btrfs_close_devices(fs_devices);
+ if (fs_devices->open_devices)
+ btrfs_close_devices(fs_devices);
error_fs_info:
free_fs_info(fs_info);
return ERR_PTR(error);
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-04-04 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 15:35 [PATCH] btrfs: close any open devices if btrfs_mount fails Eric Sandeen
2013-04-04 16:32 ` Eric Sandeen [this message]
2013-04-04 18:46 ` [PATCH V2] " Zach Brown
2013-04-04 19:45 ` Eric Sandeen
2013-04-04 19:50 ` Zach Brown
2013-04-04 20:05 ` Chris Mason
2013-04-04 20:45 ` [PATCH V3] btrfs: ignore device open failures in __btrfs_open_devices Eric Sandeen
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=515DAB1F.2050308@redhat.com \
--to=sandeen@redhat.com \
--cc=jsafrane@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.