From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PULL] uuid_mutex fixes and cleanups part2
Date: Wed, 18 Jul 2018 12:10:24 +0800 [thread overview]
Message-ID: <20180718041024.9089-1-anand.jain@oracle.com> (raw)
These patches we sent independently before and are in the mailing list.
They have been tested successfully using the xfstests. The cyclical
lockdep warning aren't due to these set of patches and they (2) can be
ignored as they are harmless because the threads involved are
ioctl/commit and mount thread which lockdep thinks is warn-able can't
co-exist in the same time space. So this set is ready to be pulled in.
Thanks.
git@github.com:asj/btrfs-devel.git misc-next-jul18
1/7 has been discussed and reviewed at length, which is drop the
unnecessary uuid_mutex in the btrfs_free_extra_devids().
2/7 fixes the race which syzbot reported.
3/7 as when we sprout we hijack the seed fs_devices, we are bringing
back the seed fs_devices using the clone_fs_devices() instead we could
use our btrfs_scan_one_device() which makes the sprout-ing operation
much cleaner.
4-7/7 are a simple cleanup patches.
Anand Jain (7):
1. btrfs: drop uuid_mutex in btrfs_free_extra_devids()
2. btrfs: fix race between free_stale_devices and close_fs_devices
3. btrfs: do device clone using the btrfs_scan_one_device
4. btrfs: use the assigned fs_devices instead of the dereference
5. btrfs: warn for num_devices below 0
6. btrfs: add helper btrfs_num_devices() to deduce num_devices
7. btrfs: add helper function check device delete able
fs/btrfs/volumes.c | 106 +++++++++++++++++++++++++++++++----------------------
1 file changed, 62 insertions(+), 44 deletions(-)
--
2.7.0
next reply other threads:[~2018-07-18 4:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 4:10 Anand Jain [this message]
2018-07-19 13:20 ` [PULL] uuid_mutex fixes and cleanups part2 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=20180718041024.9089-1-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).