From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH 0/8] Lockdep fixes
Date: Thu, 20 Aug 2020 11:18:23 -0400 [thread overview]
Message-ID: <cover.1597936173.git.josef@toxicpanda.com> (raw)
Hello,
While reworking the btrfs locking to use a rwsem I discovered a few more lockdep
issues because of the new locking. These are stand alone fixes that are safe
enough to go into 5.9, so I've broken them out from the overall locking rework.
I addressed the issues that Filipe pointed out (I think I did anyway), and run
the whole series through xfstests and saw no more lockdep messages.
fs/btrfs/ctree.c | 6 +-
fs/btrfs/dev-replace.c | 6 +-
fs/btrfs/extent-tree.c | 2 +-
fs/btrfs/extent_io.c | 8 +--
fs/btrfs/extent_io.h | 6 +-
fs/btrfs/ioctl.c | 27 ++++++---
fs/btrfs/scrub.c | 122 +++++++++++++++++++++++------------------
fs/btrfs/volumes.c | 23 ++++----
fs/btrfs/volumes.h | 3 +
9 files changed, 121 insertions(+), 82 deletions(-)
Thanks,
Josef
next reply other threads:[~2020-08-20 15:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 15:18 Josef Bacik [this message]
2020-08-20 15:18 ` [PATCH 1/8] btrfs: drop path before adding new uuid tree entry Josef Bacik
2020-08-20 15:18 ` [PATCH 2/8] btrfs: fix potential deadlock in the search ioctl Josef Bacik
2020-08-20 15:18 ` [PATCH 3/8] btrfs: move btrfs_scratch_superblocks into btrfs_dev_replace_finishing Josef Bacik
2020-08-21 12:56 ` Nikolay Borisov
2020-08-20 15:18 ` [PATCH 4/8] btrfs: move btrfs_rm_dev_replace_free_srcdev outside of all locks Josef Bacik
2020-08-20 15:18 ` [PATCH 5/8] btrfs: do not hold device_list_mutex when closing devices Josef Bacik
2020-08-20 15:18 ` [PATCH 6/8] btrfs: allocate scrub workqueues outside of locks Josef Bacik
2020-08-20 15:18 ` [PATCH 7/8] btrfs: set the correct lockdep class for new nodes Josef Bacik
2020-08-21 13:36 ` Nikolay Borisov
2020-08-20 15:18 ` [PATCH 8/8] btrfs: set the lockdep class for log tree extent buffers Josef Bacik
2020-08-21 13:43 ` Nikolay Borisov
2020-08-26 10:50 ` [PATCH 0/8] Lockdep fixes 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=cover.1597936173.git.josef@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=kernel-team@fb.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