Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Josef Bacik <josef@toxicpanda.com>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH 0/2] btrfs: fix a lockdep_assert_locked() warning
Date: Wed, 24 Aug 2022 17:12:14 +0200	[thread overview]
Message-ID: <20220824151213.GW13489@twin.jikos.cz> (raw)
In-Reply-To: <cover.1659989333.git.josef@toxicpanda.com>

On Mon, Aug 08, 2022 at 04:10:25PM -0400, Josef Bacik wrote:
> 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

Moved from topic branch to misc-next, I haven't changed the loop
iteration to the postorder macro, that can be done later.

      parent reply	other threads:[~2022-08-24 15:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 20:10 [PATCH 0/2] btrfs: fix a lockdep_assert_locked() warning Josef Bacik
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 ` David Sterba [this message]

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=20220824151213.GW13489@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=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