From: Chris Mason <chris.mason@fusionio.com>
To: Alexander Block <ablock84@googlemail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: wait_for_more_refs not waking up
Date: Mon, 6 Aug 2012 16:10:38 -0400 [thread overview]
Message-ID: <20120806201038.GE8417@shiny> (raw)
In-Reply-To: <CAB9VWqBANPS9eQ6reVDBsE-cssp_sEPK2aDAXyQHLtHkBXV_BA@mail.gmail.com>
On Fri, Aug 03, 2012 at 01:11:31AM -0600, Alexander Block wrote:
> I got a deadlock happening while creating a snapshot and ordered
> writes are pending. I can reproduce it 100% using btrfs send/receive.
> It happens when I receive a set of streams on a freshly created FS. I
> think I can exclude send/receive as the source of the problem as it
> happens while receiving, even when rebooting between send and receive.
> Receive does not depend on any extra kernel support and only uses
> normal vfs syscalls.
Are you seeing this one on the git tree I sent to Linus? I triggered
this once and then haven't seen it since I put in the barrier before the
waitqueue active check.
-chris
next prev parent reply other threads:[~2012-08-06 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 7:11 wait_for_more_refs not waking up Alexander Block
2012-08-06 20:10 ` Chris Mason [this message]
2012-08-06 20:12 ` Arne Jansen
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=20120806201038.GE8417@shiny \
--to=chris.mason@fusionio.com \
--cc=ablock84@googlemail.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).