From: Chris Mason <clm@fb.com>
To: <torvalds@linux-foundation.org>
Cc: <linux-btrfs@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Btrfs deadlock fix
Date: Sun, 23 Nov 2014 10:14:45 -0500 [thread overview]
Message-ID: <20141123151439.GA16816@ret.masoncoding.com> (raw)
Hi Linus,
My for-linus branch:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
Has a fix for a long standing deadlock that we've been trying to nail
down for a while. It ended up being a bad interaction with the fair
reader/writer locks and the order btrfs reacquires locks in the btree.
Chris Mason (1) commits (+25/-15):
btrfs: fix lockups from btrfs_clear_path_blocking
Total: (1) commits (+25/-15)
fs/btrfs/ctree.c | 14 ++------------
fs/btrfs/locking.c | 24 +++++++++++++++++++++---
fs/btrfs/locking.h | 2 ++
3 files changed, 25 insertions(+), 15 deletions(-)
next reply other threads:[~2014-11-23 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 15:14 Chris Mason [this message]
2014-11-24 0:23 ` [GIT PULL] Btrfs deadlock fix 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
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=20141123151439.GA16816@ret.masoncoding.com \
--to=clm@fb.com \
--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