From: Chris Mason <clm@fb.com>
To: <dsterba@suse.cz>
Cc: <torvalds@linux-foundation.org>, <linux-btrfs@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Btrfs deadlock fix
Date: Mon, 24 Nov 2014 13:01:10 -0500 [thread overview]
Message-ID: <1416852070.3019.5@mail.thefacebook.com> (raw)
In-Reply-To: <20141124173909.GC26471@twin.jikos.cz>
On Mon, Nov 24, 2014 at 12:39 PM, David Sterba <dsterba@suse.cz> wrote:
> Hi Chris,
>
> I thought the fix for the scrub/replace deadlock would be included in
> this pull, I can reproduce it on each run of xfstests with 3.18-rc.
>
> btrfs: fix dead lock while running replace and defrag concurrently
> https://patchwork.kernel.org/patch/5264531/
>
> I've retested it again including this pull and still deadlocks
> reliably
> at btrfs/070.
This wasn't a new problem, so I had it queued for the merge window.
-chris
next prev parent reply other threads:[~2014-11-24 18:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 15:14 [GIT PULL] Btrfs deadlock fix Chris Mason
2014-11-24 0:23 ` Benjamin Herrenschmidt
2014-11-24 0:27 ` Chris Mason
2014-11-24 3:28 ` Benjamin Herrenschmidt
2014-11-24 17:39 ` David Sterba
2014-11-24 18:01 ` Chris Mason [this message]
2014-11-24 18:27 ` 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=1416852070.3019.5@mail.thefacebook.com \
--to=clm@fb.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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