From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Josef Bacik <josef@redhat.com>
Cc: Patrick <ragamuffin@datacomm.ch>, linux-btrfs@vger.kernel.org
Subject: Possible btrfs deadlock coused by commit 660d3f6c
Date: Mon, 16 Jan 2012 09:53:23 +0100 [thread overview]
Message-ID: <20120116085322.GB2105@redhat.com> (raw)
Hi Josef,
commit 660d3f6cde552323578b85fc5a09a6742f1fe804
Author: Josef Bacik <josef@redhat.com>
Date: Fri Dec 9 11:18:51 2011 -0500
Btrfs: fix how we do delalloc reservations and how we free reservations on error
introduced possible deadlock. According to comment before
btrfs_page_mkwrite(), that function is not allowed to take
node->i_mutex .
The problem was detected by Patrick (full lockdep info is provided):
http://bugzilla.kernel.org/attachment.cgi?id=72072
during investigating of some other issue (kernel.org bug 42576)
Stanislaw
next reply other threads:[~2012-01-16 8:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 8:53 Stanislaw Gruszka [this message]
2012-01-16 14:26 ` Possible btrfs deadlock coused by commit 660d3f6c Josef Bacik
2012-01-16 20:45 ` Al Viro
2012-01-16 22:01 ` Josef Bacik
2012-01-16 22:35 ` Chris Samuel
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=20120116085322.GB2105@redhat.com \
--to=sgruszka@redhat.com \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=ragamuffin@datacomm.ch \
/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).