Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Josef Bacik <josef@toxicpanda.com>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: [PATCH 0/2] btrfs: fix a lockdep_assert_locked() warning
Date: Mon,  8 Aug 2022 16:10:25 -0400	[thread overview]
Message-ID: <cover.1659989333.git.josef@toxicpanda.com> (raw)

Hello,

With discard=async we're hitting a lockdep_assert_locked() in generic/475 in our
CI setup.  This just popped up recently because before lockdep would get
disabled before it got this far.  This series fixes the problem, and then
cleans up the cleanup functions to reduce the code and exported functions.
Thanks,

Josef

Josef Bacik (2):
  btrfs: call __btrfs_remove_free_space_cache_locked on cache load
    failure
  btrfs: remove use btrfs_remove_free_space_cache instead of variant

 fs/btrfs/block-group.c            |  2 +-
 fs/btrfs/free-space-cache.c       | 53 ++++++++++++++-----------------
 fs/btrfs/free-space-cache.h       |  1 -
 fs/btrfs/tests/btrfs-tests.c      |  2 +-
 fs/btrfs/tests/free-space-tests.c | 22 ++++++-------
 5 files changed, 37 insertions(+), 43 deletions(-)

-- 
2.26.3


             reply	other threads:[~2022-08-08 20:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 20:10 Josef Bacik [this message]
2022-08-08 20:10 ` [PATCH 1/2] btrfs: call __btrfs_remove_free_space_cache_locked on cache load failure Josef Bacik
2022-08-18 12:14   ` David Sterba
2022-08-08 20:10 ` [PATCH 2/2] btrfs: remove use btrfs_remove_free_space_cache instead of variant Josef Bacik
2022-08-24 15:12 ` [PATCH 0/2] btrfs: fix a lockdep_assert_locked() warning 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.1659989333.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