From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: "Misono, Tomohiro" <misono.tomohiro@jp.fujitsu.com>,
linux-btrfs@vger.kernel.org, David Sterba <dsterba@suse.cz>
Subject: Re: [PATCH v4 2/4] btrfs: cleanup btrfs_mount() using btrfs_mount_root()
Date: Mon, 15 Jan 2018 20:26:15 +0100 [thread overview]
Message-ID: <20180115192615.GF13726@twin.jikos.cz> (raw)
In-Reply-To: <28c4963f-9e87-ce42-7c6a-85d32cd71951@oracle.com>
On Fri, Jan 12, 2018 at 06:14:40PM +0800, Anand Jain wrote:
>
> Misono,
>
> This change is causing subsequent (subvol) mount to fail when device
> option is specified. The simplest eg for failure is ..
> mkfs.btrfs -qf /dev/sdc /dev/sdb
> mount -o device=/dev/sdb /dev/sdc /btrfs
> mount -o device=/dev/sdb /dev/sdc /btrfs1
> mount: /dev/sdc is already mounted or /btrfs1 busy
>
> Looks like
> blkdev_get_by_path() <-- is failing.
> btrfs_scan_one_device()
> btrfs_parse_early_options()
> btrfs_mount()
>
> Which is due to different holders (viz. btrfs_root_fs_type and
> btrfs_fs_type) one is used for vfs_mount and other for scan,
> so they form different holders and can't let EXCL open which
> is needed for both scan and open.
This looks close to what I see in the random test failures. I've
reverted your patch "btrfs: optimize move uuid_mutex closer to the
critical section" as I bisected to it. The uuid mutex around
blkdev_get_path probably protected the concurrent mount and scan so they
did not ask for EXCL at the same time.
Reverting (or removing the patch from the current misc-next) queue is
simpler for me ATM as I want to get to a stable base now, we can add it
later if we understand the issue with the mount/scan.
next prev parent reply other threads:[~2018-01-15 19:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 8:23 [PATCH v4 0/4] btrfs: cleanup mount path Misono, Tomohiro
2017-12-14 8:24 ` [PATCH v4 1/4] btrfs: add btrfs_mount_root() and new file_system_type Misono, Tomohiro
2017-12-14 8:25 ` [PATCH v4 2/4] btrfs: cleanup btrfs_mount() using btrfs_mount_root() Misono, Tomohiro
2018-01-12 10:14 ` Anand Jain
2018-01-15 8:24 ` Misono, Tomohiro
2018-01-15 19:26 ` David Sterba [this message]
2018-01-16 11:45 ` Anand Jain
2018-01-17 8:30 ` Misono, Tomohiro
2018-01-18 4:48 ` Anand Jain
2018-01-18 16:26 ` David Sterba
2017-12-14 8:25 ` [PATCH v4 3/4] btrfs: split parse_early_options() in two Misono, Tomohiro
2017-12-14 8:25 ` [PATCH v4 4/4] btrfs: remove unused setup_root_args() Misono, Tomohiro
2017-12-14 14:21 ` [PATCH v4 0/4] btrfs: cleanup mount path 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=20180115192615.GF13726@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=misono.tomohiro@jp.fujitsu.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