From: Chris Mason <clm@fb.com>
To: <fdmanana@kernel.org>
Cc: <linux-btrfs@vger.kernel.org>, Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH] Btrfs: remove unnecessary locking of cleaner_mutex to avoid deadlock
Date: Thu, 10 Sep 2015 09:01:05 -0400 [thread overview]
Message-ID: <20150910130105.GI9511@ret.masoncoding.com> (raw)
In-Reply-To: <1441881041-10992-1-git-send-email-fdmanana@kernel.org>
On Thu, Sep 10, 2015 at 11:30:41AM +0100, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
> This issue was discussed (in the mailing list) during the review of
> the patch titled "btrfs: explictly delete unused block groups in
> close_ctree and ro-remount" and it was agreed that acquiring the
> cleaner mutex had to be dropped after the patch titled
> "Btrfs: fix race between balance and unused block group deletion"
> got merged (both patches were submitted at about the same time, but
> one landed in kernel 4.2 and the other in the 4.3 merge window).
Thanks Filipe, hit the lockdep warning and was going to dig this out.
-chris
prev parent reply other threads:[~2015-09-10 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 10:30 [PATCH] Btrfs: remove unnecessary locking of cleaner_mutex to avoid deadlock fdmanana
2015-09-10 13:01 ` Chris Mason [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=20150910130105.GI9511@ret.masoncoding.com \
--to=clm@fb.com \
--cc=fdmanana@kernel.org \
--cc=fdmanana@suse.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;
as well as URLs for NNTP newsgroup(s).