All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH 0/3] Lockdep fixes for misc-next
Date: Mon, 19 Oct 2020 16:02:28 -0400	[thread overview]
Message-ID: <cover.1603137558.git.josef@toxicpanda.com> (raw)

Hello,

Here's a few lockdep fixes for misc-next+my rwsem patch.  Nothing too crazy, but
the last one is a little wonkey because qgroups does a backref resolution while
adding delayed refs.  Generally we do the right thing with searching the commit
roots and skipping the locking, with the exception of looking up fs roots if we
have to resolve indirect refs.  This obviously uses the normal lookup and
locking stuff, which is problematic in the new world order.  For now I'm fixing
it with a special helper for backref lookups that either finds the root in
cache, or generates a temporary root that's not inserted into the fs roots radix
tree and is only used to do the backref resolution.  Thanks,

Josef

Josef Bacik (3):
  btrfs: drop the path before adding qgroup items when enabling qgroups
  btrfs: protect the fs_info->caching_block_groups differently
  btrfs: add a helper to read the tree_root commit root for backref
    lookup

 fs/btrfs/backref.c     | 14 +++++++-
 fs/btrfs/block-group.c | 12 +++----
 fs/btrfs/disk-io.c     | 79 +++++++++++++++++++++++++++++++-----------
 fs/btrfs/disk-io.h     |  3 ++
 fs/btrfs/extent-tree.c |  2 ++
 fs/btrfs/qgroup.c      | 16 +++++++++
 6 files changed, 98 insertions(+), 28 deletions(-)

-- 
2.26.2


             reply	other threads:[~2020-10-19 20:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19 20:02 Josef Bacik [this message]
2020-10-19 20:02 ` [PATCH 1/3] btrfs: drop the path before adding qgroup items when enabling qgroups Josef Bacik
2020-10-20  9:31   ` Filipe Manana
2020-10-21 15:19   ` David Sterba
2020-10-19 20:02 ` [PATCH 2/3] btrfs: protect the fs_info->caching_block_groups differently Josef Bacik
2020-10-20 10:10   ` Filipe Manana
2020-10-21 14:05     ` Josef Bacik
2020-10-21 16:36       ` Filipe Manana
2020-10-21 18:44         ` Josef Bacik
2020-10-21 15:51   ` David Sterba
2020-10-19 20:02 ` [PATCH 3/3] btrfs: add a helper to read the tree_root commit root for backref lookup Josef Bacik
2020-10-20 11:06   ` Filipe Manana
2020-10-21 16:13 ` [PATCH 0/3] Lockdep fixes for misc-next 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.1603137558.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 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.