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] btrfs: take the correct ctl lock when removing free space cache
Date: Fri, 19 Aug 2022 22:09:46 +0200	[thread overview]
Message-ID: <20220819200946.GR13489@twin.jikos.cz> (raw)
In-Reply-To: <409ff4f5a9365bec56c6a6dc77190b7a3b3645e6.1660938272.git.josef@toxicpanda.com>

On Fri, Aug 19, 2022 at 03:44:41PM -0400, Josef Bacik wrote:
> This is a fixup for
> 
> btrfs: call __btrfs_remove_free_space_cache_locked on cache load failure
> 
> I was taking the wrong ctl lock, this can be folded into that patch.

Folded and for-next updated.

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-19 19:44 [PATCH] btrfs: take the correct ctl lock when removing free space cache Josef Bacik
2022-08-19 20:09 ` David Sterba [this message]
2022-08-19 23:01 ` kernel test robot
2022-08-20  1:39 ` kernel test robot

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=20220819200946.GR13489@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